public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/102017] New: libgcc ieee754-df.S for arm does not support exceptions Date: Mon, 23 Aug 2021 08:33:45 +0000 [thread overview] Message-ID: <bug-102017-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102017 Bug ID: 102017 Summary: libgcc ieee754-df.S for arm does not support exceptions Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: clyon at gcc dot gnu.org Target Milestone: --- As stated in libgcc/config/arm/ieee754-df.S: * Exceptions aren't supported yet, but that can be added quite easily * if necessary without impacting performances. Since I upgraded the newlib version I use in validation (moved from 3.3.0 to 4.1.0), fenv support is not enabled, thus enabling new tests in the GCC testsuite. Some of them fail at execution time on some targets because the code in libgcc does not raise exception as those tests expect: gcc.dg/torture/float32x-nan.c gcc.dg/torture/float64-nan.c gcc.dg/torture/inf-compare-1.c gcc.dg/torture/inf-compare-2.c gcc.dg/torture/inf-compare-3.c gcc.dg/torture/inf-compare-4.c gcc.dg/torture/pr52451.c This happens when targeting cortex-m4 or cortex-m33/-march=armv8-m.main+fp+dsp. These tests pass when targeting cortex-m7, because it has a DP FPU, and does not use the libgcc emulation code. Some of these tests already have xfail { powerpc*-*-* } or dg-skip-if "fenv" { powerpc-ibm-aix* }, but I am not sure whether and how we want to do this on arm (maybe using a dg-skip-if checking for -mcpu/march, but that could be painful). Or do we want to update libgcc to raise exceptions properly?
next reply other threads:[~2021-08-23 8:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-23 8:33 clyon at gcc dot gnu.org [this message] 2021-08-23 15:21 ` [Bug libgcc/102017] " rearnsha at gcc dot gnu.org 2021-08-23 19:51 ` joseph at codesourcery dot com 2021-09-24 8:59 ` clyon at gcc dot gnu.org 2022-09-22 16:44 ` torbjorn.svensson at foss dot st.com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-102017-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).