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/111839] New: Wrong code at -O3 on x86_64-linux-gnu since r12-2097-g9f34b780b0 Date: Mon, 16 Oct 2023 19:25:19 +0000 [thread overview] Message-ID: <bug-111839-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111839 Bug ID: 111839 Summary: Wrong code at -O3 on x86_64-linux-gnu since r12-2097-g9f34b780b0 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch CC: rguenth at gcc dot gnu.org Target Milestone: --- gcc at -O3 produced the wrong code. Bisected to r12-2097-g9f34b780b0 Compiler explorer: https://godbolt.org/z/Ea1hGGnob $ cat a.c int printf(const char *, ...); long a; int b, c, e, g, i; long *d, *h; char f = -26; int main() { long j; c = 0; for (; c != 7; ++c) { long k=0; long l = k; long **m = &d; for (; f + i!=0; i++) h = &l; g = h != (*m = &j); int *n = &b; *n = g; for (; e;) for (; a; a = a + 1) ; } printf("%d\n", b); } $ $ gcc -fsanitize=address,undefined a.c && ./a.out 1 $ gcc -O3 a.c && ./a.out 0 $
next reply other threads:[~2023-10-16 19:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-16 19:25 shaohua.li at inf dot ethz.ch [this message] 2023-10-16 19:28 ` [Bug tree-optimization/111839] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-10-17 3:42 ` pinskia at gcc dot gnu.org 2023-10-17 6:42 ` rguenth at gcc dot gnu.org 2024-03-05 15:58 ` jakub 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-111839-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).