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 middle-end/104196] wrong code at -O2 and above on x86_64-linux-gnu Date: Mon, 24 Jan 2022 00:17:13 +0000 [thread overview] Message-ID: <bug-104196-4-5eUxwQo9Kb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104196-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104196 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r12-4790-g4b3a325f07acebf47e82de227ce1d5ba62f5bcae Slightly adjusted testcase: int a = 6; int main () { while (1) { int b = a < 0 && 0 < -__INT_MAX__ - a ? 0 : a; if (b != 4096 - __INT_MAX__) { if (a < 6) __builtin_abort (); break; } } return 0; }
next prev parent reply other threads:[~2022-01-24 0:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 0:01 [Bug c/104196] New: " cnsun at uwaterloo dot ca 2022-01-24 0:17 ` jakub at gcc dot gnu.org [this message] 2022-01-24 0:17 ` [Bug tree-optimization/104196] [12 Regression] " jakub at gcc dot gnu.org 2022-01-24 0:37 ` pinskia at gcc dot gnu.org 2022-01-24 1:52 ` pinskia at gcc dot gnu.org 2022-01-24 2:00 ` pinskia at gcc dot gnu.org 2022-01-24 2:17 ` pinskia at gcc dot gnu.org 2022-01-24 2:19 ` pinskia at gcc dot gnu.org 2022-01-24 5:58 ` belyshev at depni dot sinp.msu.ru 2022-01-24 16:12 ` jakub at gcc dot gnu.org 2022-01-26 10:52 ` jakub at gcc dot gnu.org 2022-01-26 14:07 ` jakub at gcc dot gnu.org 2022-01-27 9:47 ` cvs-commit at gcc dot gnu.org 2022-01-27 10:20 ` 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-104196-4-5eUxwQo9Kb@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).