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/114902] New: wrong code at -O3 with "-fno-tree-vrp -fno-expensive-optimizations -fno-tree-dominator-opts" on x86_64-linux-gnu Date: Tue, 30 Apr 2024 22:13:13 +0000 [thread overview] Message-ID: <bug-114902-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114902 Bug ID: 114902 Summary: wrong code at -O3 with "-fno-tree-vrp -fno-expensive-optimizations -fno-tree-dominator-opts" 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 as it doesn't reproduce with 13.2. Compiler Explorer: https://godbolt.org/z/7ssP5W57E [587] % 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/15.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 Thread model: posix Supported LTO compression algorithms: zlib gcc version 15.0.0 20240430 (experimental) (GCC) [588] % [588] % gcctk -O3 -fno-tree-vrp -fno-expensive-optimizations -fno-tree-dominator-opts small.c [589] % ./a.out Floating point exception [590] % [590] % gcctk -O3 small.c; ./a.out [591] % [591] % cat small.c volatile int a, c; unsigned b = 1; int main() { for (; a < 2; a++) if (a) for (; c < 2; c++) { int d = -1, e = -(-d & ~b), f = -~(1 && b % a); a % f || a; if (d <= e) e = a; a = e; } return 0; }
next reply other threads:[~2024-04-30 22:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-30 22:13 zhendong.su at inf dot ethz.ch [this message] 2024-05-01 2:06 ` [Bug target/114902] [14/15 Regression] " pinskia at gcc dot gnu.org 2024-05-01 2:22 ` [Bug rtl-optimization/114902] " pinskia at gcc dot gnu.org 2024-05-01 2:34 ` pinskia at gcc dot gnu.org 2024-05-01 5:12 ` pinskia at gcc dot gnu.org 2024-05-01 5:29 ` pinskia at gcc dot gnu.org 2024-05-03 8:14 ` segher at gcc dot gnu.org 2024-05-03 8:38 ` pinskia at gcc dot gnu.org 2024-05-07 7:45 ` rguenth at gcc dot gnu.org 2024-05-09 9:48 ` segher at gcc dot gnu.org 2024-05-09 9:49 ` segher at gcc dot gnu.org 2024-05-14 20:09 ` segher at gcc dot gnu.org 2024-05-14 22:04 ` pinskia at gcc dot gnu.org 2024-05-15 16:44 ` cvs-commit at gcc dot gnu.org 2024-05-15 16:54 ` [Bug rtl-optimization/114902] [14 " jakub at gcc dot gnu.org 2024-06-04 14:26 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:28 ` jakub at gcc dot gnu.org 2024-06-11 6:17 ` cvs-commit at gcc dot gnu.org 2024-06-11 10:38 ` cvs-commit at gcc dot gnu.org 2024-06-20 13:23 ` cvs-commit 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-114902-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).