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/100740] New: wrong code at -O1 and above on x86_64-linux-gnu Date: Mon, 24 May 2021 11:10:38 +0000 [thread overview] Message-ID: <bug-100740-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100740 Bug ID: 100740 Summary: wrong code at -O1 and above 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: --- This seems to be quite long-latent, impacting GCC 9.1 and later. [636] % 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/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --disable-bootstrap --prefix=/local/suz-local/software/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib --with-system-zlib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20210524 (experimental) [master revision dc084c487e9:bd7ae6b8ef8:9d38e096c5e3b1c2233b28d0e6ff8ee81517af56] (GCC) [637] % [637] % gcctk -O0 small.c; ./a.out [638] % [638] % gcctk -O1 small.c [639] % ./a.out Aborted [640] % [640] % cat small.c unsigned a, b; int main() { unsigned c = 0; for (a = 0; a < 2; a++) for (b = 0; b < 2; b++) if (++c < a) __builtin_abort (); return 0; }
next reply other threads:[~2021-05-24 11:10 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-24 11:10 zhendong.su at inf dot ethz.ch [this message] 2021-05-24 11:25 ` [Bug tree-optimization/100740] [9/10/11/12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r9-4145 jakub at gcc dot gnu.org 2021-05-24 11:58 ` amker at gcc dot gnu.org 2021-06-01 8:20 ` rguenth at gcc dot gnu.org 2021-07-27 23:13 ` pinskia at gcc dot gnu.org 2021-09-17 10:01 ` marxin at gcc dot gnu.org 2021-10-09 17:28 ` pinskia at gcc dot gnu.org 2021-10-19 8:38 ` marxin at gcc dot gnu.org 2021-11-17 21:20 ` [Bug tree-optimization/100740] [9/10/11/12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r9-4145-ga81e2c6240655f60 pinskia at gcc dot gnu.org 2022-01-24 12:15 ` cvs-commit at gcc dot gnu.org 2022-01-24 12:46 ` [Bug tree-optimization/100740] [9/10/11 " rguenth at gcc dot gnu.org 2022-01-24 12:46 ` rguenth at gcc dot gnu.org 2022-01-26 13:12 ` rguenth at gcc dot gnu.org 2022-04-07 9:46 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug tree-optimization/100740] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:45 ` jakub at gcc dot gnu.org 2023-07-07 10:40 ` [Bug tree-optimization/100740] [11 " rguenth 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-100740-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).