From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 475C43858C56; Thu, 29 Sep 2022 09:09:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 475C43858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664442554; bh=DZmgreYEtk5TSrQfoj9AIihHGHhGmhYtGGoZrtSg9gk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RlOQb/v8i1AXoWdR1CmVU5zceN8jm108KcgcgJBj1O4tuI+uQyQSBpll5wuMzZisx utzAR1/paTF4TOqHoW+fx6FFxJS2QBaKVGAjyqC2QqbSndz2T508rA2XAXGD0OZYvr hWygAMsY/Mmg7m4kZdvCEJ0jvyAgkRGME1LISYyQ= From: "schwab@linux-m68k.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 09:09:14 +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: schwab@linux-m68k.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 #4 from Andreas Schwab --- The problem is that set_fpu_trap_exceptions does not check if feenableexcept was successful. Just because FE_* are defined does not mean that the hardw= are supports fpu exceptions of that kind (it may depend on the actual flavor of= the hardware).=