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++/110477] -fexcess-precision=standard not applied consistently
Date: Thu, 29 Jun 2023 08:04:45 +0000 [thread overview]
Message-ID: <bug-110477-4-9pOaTjXHQ4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110477-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Well "any ordinary programmer would be baffled." There is a lot of counter
intuitive parts of c and c++ and just happens to be one of them .
*** This bug has been marked as a duplicate of bug 108742 ***
next prev parent reply other threads:[~2023-06-29 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 7:28 [Bug c++/110477] New: " pdimov at gmail dot com
2023-06-29 8:00 ` [Bug c++/110477] " pdimov at gmail dot com
2023-06-29 8:04 ` pinskia at gcc dot gnu.org [this message]
2023-06-29 8:10 ` pdimov at gmail dot com
2023-06-29 8:31 ` redi at gcc dot gnu.org
2023-06-29 8:32 ` redi at gcc dot gnu.org
2023-06-29 8:44 ` pdimov at gmail dot com
2023-06-29 9:07 ` mkretz at gcc dot gnu.org
2023-06-29 11:00 ` pdimov at gmail dot com
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-110477-4-9pOaTjXHQ4@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).