public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106755] Incorrect code gen for altivec intrinsics with constant inputs
Date: Fri, 26 Aug 2022 21:01:13 +0000 [thread overview]
Message-ID: <bug-106755-4-WEh7D7rEJW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106755-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106755
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #2)
> So the tests (I've removed all static inline usage and always use
> -fno-inline) pass with -O1 and fail with -O2 and -O3. Looking at all of the
> optimizations enabled by -O2 that are not in -O1 and using -fno-* for them,
> the only option that allows the tests to pass with -O2 is
> -fno-strict-aliasing. That said, -Wall and -Wstrict-aliasing do not flag
> any warnings with the code. I suppose they could miss some issues in the
> test case code???
There are 10 cases (in just the .cc files) that use "optimize > 1", and
another 5 that do "optimize >= 2".
The -O options do more than just being shorthand for some -f option selections.
prev parent reply other threads:[~2022-08-26 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 14:30 [Bug c/106755] New: " munroesj at gcc dot gnu.org
2022-08-26 15:18 ` [Bug c/106755] " bergner at gcc dot gnu.org
2022-08-26 16:35 ` bergner at gcc dot gnu.org
2022-08-26 17:31 ` [Bug target/106755] " pinskia at gcc dot gnu.org
2022-08-26 18:38 ` bergner at gcc dot gnu.org
2022-08-26 21:01 ` segher at gcc dot gnu.org [this message]
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-106755-4-WEh7D7rEJW@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).