public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114074] [11/12/13/14 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r8-343 Date: Fri, 23 Feb 2024 11:02:48 +0000 [thread overview] Message-ID: <bug-114074-4-wEQRnXAisQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114074-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114074 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Adjusted testcase, -O0 works, -O1/-O2 aborts. int a, b, d; __attribute__((noipa)) void foo (void) { ++d; } int main () { for (a = 0; a > -3; a -= 2) { int c = a; b = __INT_MAX__ - 3000; a = ~c * b; foo (); if (!a) break; a = c; } if (d != 2) __builtin_abort (); }
next prev parent reply other threads:[~2024-02-23 11:02 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-23 10:48 [Bug tree-optimization/114074] New: wrong code at -O1 and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2024-02-23 10:54 ` [Bug tree-optimization/114074] [11/12/13/14 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r8-343 jakub at gcc dot gnu.org 2024-02-23 11:02 ` jakub at gcc dot gnu.org [this message] 2024-02-23 11:34 ` rguenth at gcc dot gnu.org 2024-02-23 12:48 ` jakub at gcc dot gnu.org 2024-02-26 9:38 ` rguenth at gcc dot gnu.org 2024-02-26 11:48 ` rguenth at gcc dot gnu.org 2024-02-26 12:03 ` rguenth at gcc dot gnu.org 2024-02-27 9:55 ` cvs-commit at gcc dot gnu.org 2024-02-27 9:57 ` [Bug tree-optimization/114074] [11/12/13 " rguenth at gcc dot gnu.org 2024-03-08 11:04 ` rguenth at gcc dot gnu.org 2024-03-08 13:41 ` cvs-commit at gcc dot gnu.org 2024-03-19 12:12 ` cvs-commit at gcc dot gnu.org 2024-03-19 12:14 ` [Bug tree-optimization/114074] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-19 12:15 ` rguenth at gcc dot gnu.org 2024-03-19 12:15 ` rguenth at gcc dot gnu.org 2024-03-19 12:16 ` 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-114074-4-wEQRnXAisQ@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).