public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103237] [10/11/12 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-linux-gnu
Date: Mon, 15 Nov 2021 10:00:55 +0000 [thread overview]
Message-ID: <bug-103237-4-QdgBU9SkuA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103237-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103237
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan.hayward at arm dot com
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> And the following fails with GCC 9 and 7 as well (using SSE vectorization).
>
> int g1;
> unsigned int g2 = 4294967295U;
> static void __attribute__((noipa)) func_1()
> {
> int *l_1 = &g1;
> for (int g3a = 0; g3a != 4; g3a++)
> for (int l_2 = 0; l_2 <= 3; l_2++)
> {
> unsigned int *l_3 = &g2;
> *l_1 = *l_3 ^= 1;
> }
> }
> int main()
> {
> func_1();
> if (g1 != -1)
> __builtin_abort ();
> return 0;
> }
This started to fail with r7-1219-gb28ead45fe630b9e.
next prev parent reply other threads:[~2021-11-15 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 17:38 [Bug tree-optimization/103237] New: " haoxintu at gmail dot com
2021-11-14 21:09 ` [Bug tree-optimization/103237] [10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-11-15 8:37 ` [Bug tree-optimization/103237] [10/11/12 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-linux-gnu since r10-1361-g9f962469cabc7fdc marxin at gcc dot gnu.org
2021-11-15 9:19 ` rguenth at gcc dot gnu.org
2021-11-15 9:50 ` rguenth at gcc dot gnu.org
2021-11-15 9:55 ` rguenth at gcc dot gnu.org
2021-11-15 10:00 ` marxin at gcc dot gnu.org [this message]
2021-11-15 10:34 ` [Bug tree-optimization/103237] [10/11/12 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-linux-gnu starting with r7-1219-gb28ead45fe630b9e rguenth at gcc dot gnu.org
2021-11-15 12:08 ` cvs-commit at gcc dot gnu.org
2021-11-22 8:00 ` [Bug tree-optimization/103237] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-02-17 10:48 ` [Bug tree-optimization/103237] [9/10 " cvs-commit at gcc dot gnu.org
2022-02-17 11:56 ` [Bug tree-optimization/103237] [9 " cvs-commit at gcc dot gnu.org
2022-02-17 11:57 ` rguenth 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-103237-4-QdgBU9SkuA@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).