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/104281] New: wrong code at -O3 Date: Sat, 29 Jan 2022 08:54:41 +0000 [thread overview] Message-ID: <bug-104281-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104281 Bug ID: 104281 Summary: wrong code at -O3 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 is a recent regression and likely related to PR 104280 and PR 104279, but it only reproduces at -O3. [537] % 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.1/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.1 20220129 (experimental) [master r12-6930-gf6f2d6cfec1] (GCC) [538] % [538] % gcctk -O2 small.c; ./a.out [539] % [539] % gcctk -O3 small.c [540] % timeout -s 9 5 ./a.out Killed [541] % [541] % cat small.c unsigned a = 1; int b, c = 2; long d; int main() { while (1) { int m = a; L: a = ~(-(m || b & d)); b = ((1 ^ a) / c); if (b) goto L; break; } return 0; }
next reply other threads:[~2022-01-29 8:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-29 8:54 zhendong.su at inf dot ethz.ch [this message] 2022-01-29 8:55 ` [Bug tree-optimization/104281] " zhendong.su at inf dot ethz.ch 2022-01-29 9:35 ` [Bug tree-optimization/104281] [12 Regression] " pinskia at gcc dot gnu.org 2022-01-29 16:55 ` cvs-commit at gcc dot gnu.org 2022-01-29 16: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-104281-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).