public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107273] New: wrong code at -O3 on x86_64-linux-gnu Date: Sat, 15 Oct 2022 20:53:04 +0000 [thread overview] Message-ID: <bug-107273-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107273 Bug ID: 107273 Summary: wrong code at -O3 on x86_64-linux-gnu Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: --- It appears to be a recent regression. Compiler Explorer: https://godbolt.org/z/Mo8sPhYW7 [538] % gcctk -v Using built-in specs. COLLECT_GCC=gcctk COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --disable-bootstrap --enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk --enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib --with-system-zlib Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20221015 (experimental) [master r13-3311-gbaeec7cc83b] (GCC) [539] % [539] % gcctk -O2 small.c; ./a.out [540] % [540] % gcctk -O3 small.c [541] % ./a.out Segmentation fault [542] % [542] % cat small.c int printf(const char *, ...); int a[1] = {1}; short b, c = 5500; int d; long e; char f = 1; int main() { while (1) { long g = b < 1; e = g; break; } for (; f; f--) { if (e) { d = -(6L | -(c & 1000)); } char h = d; if (b) b = 0; if (d < 200) while (1) printf("%d", a[c]); short i = h * 210; c = i; } return 0; }
next reply other threads:[~2022-10-15 20:53 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-15 20:53 zhendong.su at inf dot ethz.ch [this message] 2022-10-15 20:57 ` [Bug tree-optimization/107273] " zhendong.su at inf dot ethz.ch 2022-10-15 21:00 ` zhendong.su at inf dot ethz.ch 2022-10-15 21:04 ` zhendong.su at inf dot ethz.ch 2022-10-17 3:21 ` crazylht at gmail dot com 2022-10-17 7:55 ` rguenth at gcc dot gnu.org 2022-10-17 16:12 ` hjl.tools at gmail dot com 2022-10-17 19:05 ` [Bug tree-optimization/107273] wrong code at -O3 on x86_64-linux-gnu by r13-3281 hjl.tools at gmail dot com 2022-10-17 19:07 ` hjl.tools at gmail dot com 2022-10-17 20:42 ` hjl.tools at gmail dot com 2022-10-17 21:03 ` amacleod at redhat dot com 2022-10-18 1:05 ` cvs-commit at gcc dot gnu.org 2022-10-18 1:05 ` amacleod at redhat dot com
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-107273-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).