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/111648] New: Wrong code at -O2/3 on x86_64-linux-gnu since r14-3243-ga7dba4a1c05 Date: Sat, 30 Sep 2023 14:04:21 +0000 [thread overview] Message-ID: <bug-111648-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111648 Bug ID: 111648 Summary: Wrong code at -O2/3 on x86_64-linux-gnu since r14-3243-ga7dba4a1c05 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: prathamesh3492 at gcc dot gnu.org Target Milestone: --- gcc at -O2/3 produced the wrong code Bisected to r14-3243-ga7dba4a1c05 Compiler explorer: https://godbolt.org/z/1bvWTrEK1 $ cat a.c int printf(const char *, ...); int a; int *b = &a; static int **c = &b; static int d; short e; char f; int main() { f = -21; for (; f < -5; f++) { e = f ^ 3; d = *b; **c = e; } printf("%d\n", d); } $ $ gcc -O0 a.c && ./a.out -6 $ gcc -O2 a.c && ./a.out 2 $
next reply other threads:[~2023-09-30 14:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-30 14:04 shaohua.li at inf dot ethz.ch [this message] 2023-09-30 16:48 ` [Bug tree-optimization/111648] " prathamesh3492 at gcc dot gnu.org 2023-10-01 18:49 ` [Bug tree-optimization/111648] [14 Regression] " pinskia at gcc dot gnu.org 2023-10-03 12:19 ` prathamesh3492 at gcc dot gnu.org 2023-10-03 12:21 ` prathamesh3492 at gcc dot gnu.org 2023-10-04 9:25 ` rguenth at gcc dot gnu.org 2023-10-18 19:04 ` cvs-commit at gcc dot gnu.org 2023-10-18 19:06 ` prathamesh3492 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-111648-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).