Searched refs:exception_domain_is_secure (Results 1 – 2 of 2) sorted by relevance
3558 bool exception_domain_is_secure = false; in arm_m_exception_cache() local3568 exception_domain_is_secure = (bit (lr, 0) != 0); in arm_m_exception_cache()3574 if (secure_stack_used && !exception_domain_is_secure in arm_m_exception_cache()3678 && (!default_callee_register_stacking || !exception_domain_is_secure)) in arm_m_exception_cache()
94981 exception_domain_is_secure = (bit (lr, 0) == 0);94990 && (!default_callee_register_stacking || exception_domain_is_secure))95001 So we should test for !exception_domain_is_secure instead of non-negated95005 But another test of exception_domain_is_secure (negated due to the95012 if (secure_stack_used && !exception_domain_is_secure95057 Set exception_domain_is_secure to the value expected by its name.95058 Fix exception_domain_is_secure usage in the additional state context