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 03:19:21 +0000 [thread overview]
Message-ID: <bug-114181-4-oODgrb2UsD@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 #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to g.peterhoff from comment #12)
> Are there already plans how to deal with the
> https://en.cppreference.com/w/c/experimental/fpext1
> https://en.cppreference.com/w/c/experimental/fpext4
> regarding C++?
Well dfp is supported, or kinda of supported already for GCC, see PR 51364
also.
as far as fpext4 is concern, I suspect it might be better to take it up with
the C++ standards committee ...
next prev parent reply other threads:[~2024-03-01 3:19 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
2024-03-01 3:08 ` g.peterhoff@t-online.de
2024-03-01 3:19 ` pinskia at gcc dot gnu.org [this message]
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-oODgrb2UsD@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: link
Be 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).