public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114181] issubnormal is a macro Date: Fri, 01 Mar 2024 02:38:38 +0000 [thread overview] Message-ID: <bug-114181-4-obI7THTdj5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114181-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114181 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> --- In this case gcc has nothing to do with this. Since defining issubnormal inside std is undefined behavior there is nothing to be done. Also you don't need a builtin since fpclassify is there already. When issubnormal is added to the c++ standard, libstdc++'s will add it too.
next prev parent reply other threads:[~2024-03-01 2:38 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 0:27 [Bug c/114181] New: " g.peterhoff@t-online.de 2024-03-01 0:32 ` [Bug c/114181] " pinskia at gcc dot gnu.org 2024-03-01 0:35 ` pinskia at gcc dot gnu.org 2024-03-01 0:41 ` g.peterhoff@t-online.de 2024-03-01 0:51 ` pinskia at gcc dot gnu.org 2024-03-01 1:04 ` g.peterhoff@t-online.de 2024-03-01 1:07 ` pinskia at gcc dot gnu.org 2024-03-01 1:08 ` pinskia at gcc dot gnu.org 2024-03-01 1:14 ` g.peterhoff@t-online.de 2024-03-01 1:17 ` pinskia at gcc dot gnu.org 2024-03-01 2:20 ` g.peterhoff@t-online.de 2024-03-01 2:38 ` pinskia at gcc dot gnu.org [this message] 2024-03-01 3:08 ` g.peterhoff@t-online.de 2024-03-01 3:19 ` pinskia at gcc dot gnu.org 2024-03-01 11:05 ` redi at gcc dot gnu.org 2024-03-01 11:19 ` 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-114181-4-obI7THTdj5@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).