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++/110622] x86: Miscompilation at O1 level (O0 is working)
Date: Tue, 11 Jul 2023 06:38:19 +0000 [thread overview]
Message-ID: <bug-110622-4-jWf4V5KdKm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110622-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Mathieu Malaterre from comment #5)
> > Does adding -fexcess-precision=standard help? What about -ffloat-store ?
>
> highway is c++ only. Those flags are C only
No they are not. -fexcess-precision=standard C++ was added for GCC 13.
-ffloat-store is generic middle-end option and has been supported by all
front-ends since at least GCC 3.
next prev parent reply other threads:[~2023-07-11 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 6:28 [Bug c++/110622] New: " malat at debian dot org
2023-07-11 6:29 ` [Bug c++/110622] " malat at debian dot org
2023-07-11 6:30 ` malat at debian dot org
2023-07-11 6:31 ` pinskia at gcc dot gnu.org
2023-07-11 6:33 ` malat at debian dot org
2023-07-11 6:33 ` malat at debian dot org
2023-07-11 6:38 ` pinskia at gcc dot gnu.org [this message]
2023-07-11 6:44 ` [Bug target/110622] " malat at debian dot org
2023-07-11 8:25 ` malat at debian dot org
2023-09-21 9:44 ` malat at debian dot org
2023-09-21 9:48 ` [Bug target/110622] x87: Miscompilation at O2 level (O1 " malat at debian dot org
2023-09-21 9:51 ` malat at debian dot org
2023-09-21 9:56 ` malat at debian dot org
2023-09-21 13:33 ` pinskia at gcc dot gnu.org
2023-09-21 13:42 ` malat at debian dot org
2023-09-21 13:45 ` xry111 at gcc dot gnu.org
2023-09-21 14:29 ` malat at debian dot 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-110622-4-jWf4V5KdKm@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).