public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110176] wrong code at -Os and above on x86_64-linux-gnu Date: Thu, 08 Jun 2023 21:50:00 +0000 [thread overview] Message-ID: <bug-110176-4-GUCBEnNhFV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110176-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110176 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-06-08 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase which will abort rather than do an infinite loop: ``` int f(_Bool t) { int tt = t; unsigned x = -1; int xx = x; return xx <= tt; } int a, b; void c() {} [[gnu::noipa]] void h() {__builtin_abort();} int d() { unsigned f[1]; int i; if (a) goto h; f[0] = -1; while (1) { c(); for (; a < 1; a++) { if (0) { j: continue; } i = f[0]; if (a) break; b = i >= (b == 0); } if (!b) { if (0) { h: goto j; } return 0; } h(); } } int main() { d(); return 0; } ```
next prev parent reply other threads:[~2023-06-08 21:50 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-08 14:44 [Bug tree-optimization/110176] New: " zhendong.su at inf dot ethz.ch 2023-06-08 21:43 ` [Bug tree-optimization/110176] " pinskia at gcc dot gnu.org 2023-06-08 21:50 ` pinskia at gcc dot gnu.org [this message] 2023-06-08 21:52 ` [Bug tree-optimization/110176] [10/11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-08 22:10 ` pinskia at gcc dot gnu.org 2023-06-09 7:11 ` rguenth at gcc dot gnu.org 2023-07-07 10:45 ` [Bug tree-optimization/110176] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-01-04 12:31 ` [Bug tree-optimization/110176] [11/12/13/14 Regression] wrong code at -Os and above on x86_64-linux-gnu since r11-2446 jakub at gcc dot gnu.org 2024-01-04 17:17 ` pinskia at gcc dot gnu.org 2024-01-08 9:37 ` rguenth at gcc dot gnu.org 2024-01-31 13:44 ` rguenth at gcc dot gnu.org 2024-01-31 14:47 ` cvs-commit at gcc dot gnu.org 2024-01-31 14:49 ` [Bug tree-optimization/110176] [11/12/13 " rguenth at gcc dot gnu.org 2024-02-06 13:20 ` cvs-commit at gcc dot gnu.org 2024-05-17 11:12 ` [Bug tree-optimization/110176] [11/12 " 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-110176-4-GUCBEnNhFV@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).