From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DC0423858D38; Thu, 22 Sep 2022 16:44:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DC0423858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663865065; bh=qn0WkNQZTrDQ/rP4BQQ4kLni7eZxXGk4ms5ex8SgjlM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EvtNGFyjQ+5n4OvHdf6JuYB/SgNyGhfHQ2yHFfe9A7rO/yK8fZVRKPBb/Vl7iyf1M dXWYDgxv7TgYgUGSN/mJ+YsQglfat8Cltc9GFKRc+flHp/n6drN2/l/8r3wCBnM83v r1FJstbkPhh3tE1L/WDJZIa/ev+p0PcjSyF2p9WY= From: "torbjorn.svensson at foss dot st.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/102017] libgcc ieee754-df.S for arm does not support exceptions Date: Thu, 22 Sep 2022 16:44:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: torbjorn.svensson at foss dot st.com X-Bugzilla-Status: UNCONFIRMED 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: cc 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=3D102017 Torbj=C3=B6rn SVENSSON changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |torbjorn.svensson at foss = dot st.c | |om --- Comment #4 from Torbj=C3=B6rn SVENSSON --- I made an attempt to handle this for Arm as the number of failed tests rela= ted to this is growing with each new GCC version... Please review this patch https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602025.html and gi= ve me your feedback. Is this the right way to go? Is there a better way to go in order to avoid filling the log with fails th= at is not going to be addressed?=