public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110796] builtin_iseqsig fails some tests in armv8l-linux-gnueabihf Date: Fri, 05 Jan 2024 14:49:39 +0000 [thread overview] Message-ID: <bug-110796-4-gz8agOOf2O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110796-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110796 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #13 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- (In reply to Francois-Xavier Coudert from comment #8) > (In reply to Richard Earnshaw from comment #6) > > Is the exception status supposed to be in a defined state when the test > > runs? Shouldn't there be a call to feclearexcept (FE_ALL_EXCEPT) at the > > start of the test? > > Isn't the exception status guaranteed to be defined (and not signaling) when > the program starts? It should be guaranteed. Otherwise it indicates a bug in kernel or libc. > But adding feclearexcept (FE_ALL_EXCEPT); at the beginning of main() could > not hurt, for sure.
prev parent reply other threads:[~2024-01-05 14:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 22:36 [Bug middle-end/110796] New: " thiago.bauermann at linaro dot org 2023-07-24 22:39 ` [Bug target/110796] " pinskia at gcc dot gnu.org 2023-07-24 22:50 ` thiago.bauermann at linaro dot org 2023-07-25 15:13 ` fxcoudert at gcc dot gnu.org 2023-07-25 16:44 ` thiago.bauermann at linaro dot org 2023-07-25 16:50 ` fxcoudert at gcc dot gnu.org 2023-07-25 17:13 ` rearnsha at gcc dot gnu.org 2023-07-25 17:14 ` thiago.bauermann at linaro dot org 2023-07-25 17:17 ` fxcoudert at gcc dot gnu.org 2023-07-25 17:18 ` rearnsha at gcc dot gnu.org 2023-07-25 17:48 ` thiago.bauermann at linaro dot org 2023-07-26 16:58 ` rearnsha at gcc dot gnu.org 2023-08-02 10:38 ` rearnsha at gcc dot gnu.org 2024-01-05 14:49 ` xry111 at gcc dot gnu.org [this message]
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-110796-4-gz8agOOf2O@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).