public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malat at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106322] i386: Wrong code at O2 level (O0 / O1 are working)
Date: Wed, 03 Aug 2022 08:41:12 +0000 [thread overview]
Message-ID: <bug-106322-4-aVkb43S1lE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106322-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #11 from Mathieu Malaterre <malat at debian dot org> ---
(In reply to Uroš Bizjak from comment #10)
> The reason the test fails with gcc-12 is that gcc-12 enabled
> auto-vectorisation for -O2.
I can make the symptoms go away by doing: `-O2 -fno-tree-vectorize`. Since this
affects also arm5 and powerpc, it seems the bug is somewhere in the shared
32bits code (bug does not affects 64bits arch for some reason).
next prev parent reply other threads:[~2022-08-03 8:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:48 [Bug c++/106322] New: " malat at debian dot org
2022-07-16 9:55 ` [Bug c++/106322] " malat at debian dot org
2022-07-16 10:00 ` malat at debian dot org
2022-07-16 10:00 ` malat at debian dot org
2022-07-16 10:02 ` malat at debian dot org
2022-07-16 10:02 ` malat at debian dot org
2022-07-16 10:07 ` malat at debian dot org
2022-07-16 10:15 ` malat at debian dot org
2022-07-17 20:20 ` [Bug target/106322] " pinskia at gcc dot gnu.org
2022-07-18 8:48 ` marxin at gcc dot gnu.org
2022-07-18 14:40 ` malat at debian dot org
2022-07-19 7:58 ` ubizjak at gmail dot com
2022-08-03 8:41 ` malat at debian dot org [this message]
2022-08-03 12:31 ` [Bug tree-optimization/106322] 32bits / tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) malat at debian dot org
2022-08-03 12:32 ` malat at debian dot org
2022-08-03 12:33 ` malat at debian dot org
2022-08-05 13:14 ` [Bug tree-optimization/106322] " malat at debian dot org
2022-08-08 7:12 ` malat at debian dot org
2022-08-08 7:20 ` malat at debian dot org
2022-08-08 10:00 ` malat at debian dot org
2022-08-09 7:50 ` malat at debian dot org
2022-08-09 12:36 ` marxin at gcc dot gnu.org
2022-08-09 12:58 ` malat at debian dot org
2022-08-09 13:00 ` ubizjak at gmail dot com
2022-08-09 13:03 ` malat at debian dot org
2022-08-09 13:04 ` marxin at gcc dot gnu.org
2022-08-09 13:05 ` malat at debian dot org
2022-08-09 13:11 ` [Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5 marxin at gcc dot gnu.org
2022-08-09 13:12 ` marxin at gcc dot gnu.org
2022-08-09 13:26 ` linkw at gcc dot gnu.org
2022-08-09 13:29 ` marxin at gcc dot gnu.org
2022-08-09 13:30 ` malat at debian dot org
2022-08-09 13:34 ` malat at debian dot org
2022-08-09 13:40 ` linkw at gcc dot gnu.org
2022-08-09 13:48 ` rguenth at gcc dot gnu.org
2022-08-09 13:53 ` malat at debian dot org
2022-08-09 13:56 ` malat at debian dot org
2022-08-09 14:01 ` malat at debian dot org
2022-08-09 15:28 ` pinskia at gcc dot gnu.org
2022-08-10 5:25 ` linkw at gcc dot gnu.org
2022-08-10 5:34 ` linkw at gcc dot gnu.org
2022-08-10 6:03 ` pinskia at gcc dot gnu.org
2022-08-10 6:24 ` linkw at gcc dot gnu.org
2022-08-10 9:47 ` linkw at gcc dot gnu.org
2022-08-10 12:32 ` rguenth at gcc dot gnu.org
2022-08-10 12:36 ` rguenth at gcc dot gnu.org
2022-08-11 1:18 ` linkw at gcc dot gnu.org
2022-08-15 6:51 ` linkw at gcc dot gnu.org
2022-08-16 5:50 ` cvs-commit at gcc dot gnu.org
2022-08-24 2:31 ` [Bug tree-optimization/106322] [12 " cvs-commit at gcc dot gnu.org
2022-08-24 2:53 ` linkw at gcc dot gnu.org
2022-08-24 6:51 ` rguenth at gcc dot gnu.org
2022-09-27 14:14 ` malat at debian dot org
2022-09-27 14:18 ` malat at debian dot org
2022-09-28 6:11 ` malat at debian dot org
2022-09-28 6:26 ` linkw 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-106322-4-aVkb43S1lE@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).