public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert 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: Tue, 25 Jul 2023 16:50:03 +0000 [thread overview] Message-ID: <bug-110796-4-AWIdILlA4j@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 --- Comment #5 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- OK, so it signals FE_INVALID on the first test. Can you run this with the same options, and see what happens? ------- #include <fenv.h> #include <stdio.h> void ftrue (float x, float y) { if (!__builtin_iseqsig (x, y)) __builtin_abort (); } int main () { volatile float f1, f2; f1 = 0.f; f2 = 0.f; if (fetestexcept (FE_INVALID)) printf("Invalid 1\n"); ftrue (f1, f2); if (fetestexcept (FE_INVALID)) printf("Invalid 2\n"); return 0; } ------- One surprising thing is that the directive "dg-add-options ieee" in the test did not apparently add any other option for IEEE conformance…
next prev parent reply other threads:[~2023-07-25 16:50 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 [this message] 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
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-AWIdILlA4j@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).