From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B6E7B3857C60; Thu, 29 Sep 2022 15:19:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B6E7B3857C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664464743; bh=tghFnPR1M8dcdlRwPCydWnzgajXnoabUCLwL1TVyFk8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GHjw7X9Yz4CINIzwhBozebVMCkC/LIiwLK/Ek0pmhVx0S56yMSF3wpOLdubak8pt1 vwS9/QKBJd+TTVGcya1z7p7Q0E24a4/iFnfBg6tneTGAj8U3NgwZMU6Rh0yhMdKqbx umybmDYJdxr6U2ILSMPH97e9mdHwgGQHmscNZ9dg= From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107071] gfortran.dg/ieee/modes_1.f90 fails on aarch64-linux Date: Thu, 29 Sep 2022 15:19:03 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107071 --- Comment #6 from Richard Earnshaw --- Whilst the patch is probably fine and a better way of doing this, it won't = fix the test failure. I think your problem is that you're assuming that an exception will cause a trap in hardware. That's not how IEEE says FP exceptions have to work. On aarch64, for most implementations the exceptio= ns are accumulated in a status register and you have to read that register to = see if an FP exception occurred.=