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 c/110252] New: Wrong code at -O2/3/s on x86_64-linux-gnu Date: Wed, 14 Jun 2023 14:52:29 +0000 [thread overview] Message-ID: <bug-110252-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110252 Bug ID: 110252 Summary: Wrong code at -O2/3/s on x86_64-linux-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch Target Milestone: --- This seems to be a recent regression. Compiler explorer: https://godbolt.org/z/TW97cdYxv $ cat a.c int printf(const char *, ...); int d, f; const char a = 239; short e, b, h = 2; long g; short *c = &e; int *i = &f; int(j)(int k, int l) { return k < 0 ? k : k >> l; } int main() { for (;;) { g = (char)d + a; b = h && j(g, 6); *c = b; *i = e; break; } printf("%d\n", f); } $ $ gcc-tk -O0 a.c && ./a.out 1 $ gcc-tk -O1 a.c && ./a.out 1 $ gcc-tk -O2 a.c && ./a.out -1 $ gcc-tk -O3 a.c && ./a.out -1 $ gcc-tk -Os a.c && ./a.out -1 $ $ gcc-tk -v Using built-in specs. COLLECT_GCC=gcc-tk COLLECT_LTO_WRAPPER=/zdata/shaoli/compilers/ccbuilder-compilers/gcc-bf470895905e9152424076d1630a9d2c60de023b/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --disable-multilib --disable-bootstrap --enable-languages=c,c++ --prefix=/zdata/shaoli/compilers/ccbuilder-compilers/gcc-bf470895905e9152424076d1630a9d2c60de023b Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20230612 (experimental) (GCC) $
next reply other threads:[~2023-06-14 14:52 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-14 14:52 shaohua.li at inf dot ethz.ch [this message] 2023-06-14 16:13 ` [Bug tree-optimization/110252] [14 Regression] " pinskia at gcc dot gnu.org 2023-06-14 21:09 ` pinskia at gcc dot gnu.org 2023-06-15 2:13 ` pinskia at gcc dot gnu.org 2023-06-15 3:11 ` pinskia at gcc dot gnu.org 2023-06-15 6:22 ` rguenth at gcc dot gnu.org 2023-06-15 6:22 ` rguenth at gcc dot gnu.org 2023-06-21 22:51 ` pinskia at gcc dot gnu.org 2023-06-22 15:36 ` pinskia at gcc dot gnu.org 2023-06-28 20:31 ` pinskia at gcc dot gnu.org 2023-06-28 20:35 ` pinskia at gcc dot gnu.org 2023-06-29 9:22 ` zhendong.su at inf dot ethz.ch 2023-06-29 15:42 ` pinskia at gcc dot gnu.org 2023-06-30 5:18 ` pinskia at gcc dot gnu.org 2023-07-03 11:31 ` pinskia at gcc dot gnu.org 2023-07-06 6:12 ` pinskia at gcc dot gnu.org 2023-07-08 17:16 ` pinskia at gcc dot gnu.org 2023-07-15 3:21 ` pinskia at gcc dot gnu.org 2023-07-19 7:41 ` pinskia at gcc dot gnu.org 2023-07-19 16:19 ` cvs-commit at gcc dot gnu.org 2023-07-19 16:19 ` 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-110252-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).