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 fortran/106579] ieee_signaling_nan problem in fortran on powerpc64 Date: Thu, 11 Aug 2022 11:26:44 +0000 [thread overview] Message-ID: <bug-106579-4-LdRkWmRajD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106579-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106579 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-08-11 --- Comment #5 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- Previous discussion on the list: - when I first implemented it in 2013: https://gcc.gnu.org/legacy-ml/gcc/2013-11/msg00109.html - more recent: https://www.mail-archive.com/gcc@gcc.gnu.org/msg97340.html I think Joseph pointed (either in another bugzilla issue, or on the list) to a first tentative implementation of __builtin_issignaling in the middle-end by Sandra Loosemore, which had to be reversed because it caused trouble on some targets. The difficulty that was cited (and why I didn't get to it myself) is the large number of floating-point formats to be handled. That said, having __builtin_issignaling() would be great and we could emit a lot more of the IEEE functions in the front-end, if it were available.
next prev parent reply other threads:[~2022-08-11 11:26 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-10 15:14 [Bug fortran/106579] New: " seurer at gcc dot gnu.org 2022-08-10 17:51 ` [Bug fortran/106579] " jakub at gcc dot gnu.org 2022-08-10 22:46 ` segher at gcc dot gnu.org 2022-08-11 7:52 ` fxcoudert at gcc dot gnu.org 2022-08-11 9:55 ` jakub at gcc dot gnu.org 2022-08-11 11:26 ` fxcoudert at gcc dot gnu.org [this message] 2022-08-11 16:22 ` jakub at gcc dot gnu.org 2022-08-11 20:35 ` jakub at gcc dot gnu.org 2022-08-12 11:19 ` jakub at gcc dot gnu.org 2022-08-12 17:15 ` jakub at gcc dot gnu.org 2022-08-26 7:53 ` cvs-commit at gcc dot gnu.org 2022-08-26 7:56 ` cvs-commit at gcc dot gnu.org 2022-08-26 8:05 ` jakub at gcc dot gnu.org 2022-08-29 10:06 ` cvs-commit at gcc dot gnu.org 2022-08-29 10:06 ` cvs-commit at gcc dot gnu.org 2022-08-30 9:10 ` 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-106579-4-LdRkWmRajD@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).