public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shaohua.li at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111519] New: [13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu since r13-455-g1fe04c497d Date: Thu, 21 Sep 2023 13:20:27 +0000 [thread overview] Message-ID: <bug-111519-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111519 Bug ID: 111519 Summary: [13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu since r13-455-g1fe04c497d Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch CC: roger at nextmovesoftware dot com Target Milestone: --- gcc at -O3 produced the wrong code. Bisected to r13-455-g1fe04c497d Compiler explorer: https://godbolt.org/z/ozEaKa1rY $ cat a.c int printf(const char *, ...); int a, o; char b, f, i; long c; static signed char d; static char g; unsigned *h; signed char *e = &f; static signed char **j = &e; static long k[2]; unsigned **l = &h; short m; int main(int q, char *r[]) { int p = 0; if (q == 0) p = 1; signed char *n = &d; *n = 0; for (; c;) for (; i; i--) ; g = 0; for (; g <= 1; g++) { *n = **j; k[g] = 0 != &m; *e = l && k[0]; } if (p) printf(&b); for (; o < 4; o++) { a = d; if (p) printf(&b); } printf("%d\n", a); } $ $ gcc -O2 a.c && ./a.out 1 $ gcc -O3 a.c && ./a.out 0 $
next reply other threads:[~2023-09-21 13:20 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 13:20 shaohua.li at inf dot ethz.ch [this message] 2023-09-21 15:35 ` [Bug tree-optimization/111519] " pinskia at gcc dot gnu.org 2023-09-21 15:47 ` pinskia at gcc dot gnu.org 2023-09-21 16:00 ` rguenth at gcc dot gnu.org 2023-10-09 22:05 ` roger at nextmovesoftware dot com 2023-10-10 7:56 ` rguenth at gcc dot gnu.org 2023-10-10 8:21 ` jakub at gcc dot gnu.org 2023-10-10 8:26 ` rguenth at gcc dot gnu.org 2023-10-10 8:31 ` rguenth at gcc dot gnu.org 2023-10-10 8:33 ` rguenth at gcc dot gnu.org 2023-10-10 10:37 ` rguenth at gcc dot gnu.org 2023-10-11 7:09 ` cvs-commit at gcc dot gnu.org 2023-10-11 7:23 ` cvs-commit at gcc dot gnu.org 2023-10-11 7:24 ` jakub at gcc dot gnu.org 2023-11-02 9:05 ` pinskia 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-111519-4@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: linkBe 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).