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/103300] [12 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-4526-gd8edfadfc7a9795b
Date: Thu, 02 Dec 2021 09:14:02 +0000 [thread overview]
Message-ID: <bug-103300-4-bx5ieV3bTY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103300-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103300
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Zhendong Su from comment #6)
> Another test likely for the same issue:
>
> [652] % gcctk -O3 small.c; ./a.out
> Aborted
> [653] % gcctk -O2 -floop-unroll-and-jam small.c; ./a.out
> Aborted
> [654] % cat small.c
> int printf(const char *, ...);
> int a[2], b, c, d, e;
> int main() {
> if (b) {
> printf("0");
> goto L2;
> }
> L1:
> b = 0;
> L2:
> if (d)
> L3:
> goto L1;
> if (e)
> goto L3;
> if (c)
> goto L2;
> for (b = 0; b < 3; b++)
> for (d = 0; d < 2; d++)
> a[d] ^= 1;
> if (a[1] != 1)
> __builtin_abort();
> return 0;
> }
Yes, started with the same revision.
next prev parent reply other threads:[~2021-12-02 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:17 [Bug tree-optimization/103300] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2021-11-17 10:24 ` [Bug tree-optimization/103300] [12 Regression] " pinskia at gcc dot gnu.org
2021-11-17 11:08 ` [Bug tree-optimization/103300] New: " Jan Hubicka
2021-11-17 11:08 ` [Bug tree-optimization/103300] [12 Regression] " hubicka at kam dot mff.cuni.cz
2021-11-17 22:32 ` pinskia at gcc dot gnu.org
2021-11-18 7:47 ` rguenth at gcc dot gnu.org
2021-11-18 10:37 ` rguenth at gcc dot gnu.org
2021-11-18 10:39 ` [Bug tree-optimization/103300] [12 Regression] wrong code at -O3 on x86_64-linux-gnu since r12-4526-gd8edfadfc7a9795b marxin at gcc dot gnu.org
2021-12-02 7:22 ` zhendong.su at inf dot ethz.ch
2021-12-02 9:14 ` marxin at gcc dot gnu.org [this message]
2022-02-15 12:53 ` 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-103300-4-bx5ieV3bTY@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).