From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 8A9303858D32; Mon,  3 Oct 2022 09:19:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A9303858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664788775;
	bh=223GvUN41ewiuiPbafux/IK2cyTJmFbiU77wH/ict3M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Jnyize3MPmnPyydIQCxJ7OnEGPwBRV/wPoCHjCBawrWPsaml4bQSY7FxPbz3mx1d0
	 nn09z6Pjd0wmHHxFY2c+WGYTa/iv1q9tKaILP2Mgi7nXmIDxtP+7eBiF9ebVix0As2
	 NCwoTxiaIu5WZI6fhhBQm6VXf2u7Utm3pHIAf/S8=
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107071] gfortran.dg/ieee/modes_1.f90 fails on
 aarch64-linux
Date: Mon, 03 Oct 2022 09:19:35 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107071-4-xXz3rxbWgi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107071

--- Comment #10 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
That sounds broadly sensible.  One optimization might be to check if the
exception trapping is already enabled, then you can skip the read/set/resto=
re
dance entirely in that case. That might be more efficient on some hardware =
as
changing the flags might cause a pipeline bubble.

The same is also true for the other tests where you do a read/set/restore
sequence.=