public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "k3x-devel at outlook dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/115374] fmod() in x86_64 -O3 not using return value from the glibc's implementation if x87 FPU fprem returns NaN Date: Thu, 06 Jun 2024 19:13:27 +0000 [thread overview] Message-ID: <bug-115374-4-SmrYKd7iII@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115374-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115374 Mario Hros <k3x-devel at outlook dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58371|0 |1 is obsolete| | --- Comment #3 from Mario Hros <k3x-devel at outlook dot com> --- Created attachment 58372 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58372&action=edit reporoduction code, compile with -O3 -lm Prints "is NaN and should not be"
next prev parent reply other threads:[~2024-06-06 19:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-06 19:01 [Bug c/115374] New: " k3x-devel at outlook dot com 2024-06-06 19:04 ` [Bug c/115374] " pinskia at gcc dot gnu.org 2024-06-06 19:06 ` pinskia at gcc dot gnu.org 2024-06-06 19:13 ` k3x-devel at outlook dot com [this message] 2024-06-06 19:15 ` k3x-devel at outlook dot com 2024-06-06 19:18 ` pinskia at gcc dot gnu.org 2024-06-06 19:20 ` pinskia at gcc dot gnu.org 2024-06-06 19:28 ` k3x-devel at outlook dot com 2024-06-06 19:32 ` ubizjak at gmail dot com 2024-06-07 6:09 ` rguenth at gcc dot gnu.org 2024-06-07 15:20 ` k3x-devel at outlook dot com 2024-06-07 15:23 ` jakub at gcc dot gnu.org 2024-06-07 15:30 ` k3x-devel at outlook dot com 2024-06-07 15:34 ` jakub 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-115374-4-SmrYKd7iII@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).