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/104604] [12 Regression]wrong code with -O2 VRP Complex integer division issue Date: Sat, 19 Feb 2022 08:10:17 +0000 [thread overview] Message-ID: <bug-104604-4-MdSO3AbgPD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104604-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104604 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.2.0 Target Milestone|--- |12.0 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|wrong code with -O2 |[12 Regression]wrong code |-fconserve-stack |with -O2 VRP Complex |--param=vrp1-mode=ranger |integer division issue Last reconfirmed| |2022-02-19 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed, reduced testcase which shows the problem even at just -O2: typedef unsigned char u8; u8 g; __attribute__((noipa)) u8 foo (_Complex unsigned c) { _Complex unsigned t = 3; t /= c; u8 v = g; return v + t; } int main (void) { u8 x = foo (7); if (x) __builtin_abort (); return 0; }
next prev parent reply other threads:[~2022-02-19 8:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-19 7:55 [Bug tree-optimization/104604] New: wrong code with -O2 -fconserve-stack --param=vrp1-mode=ranger zsojka at seznam dot cz 2022-02-19 8:10 ` pinskia at gcc dot gnu.org [this message] 2022-02-21 9:44 ` [Bug tree-optimization/104604] [12 Regression]wrong code with -O2 VRP Complex integer division issue rguenth at gcc dot gnu.org 2022-02-21 12:40 ` [Bug tree-optimization/104604] [12 Regression]wrong code with -O2 VRP Complex integer division issue since r12-3328 jakub at gcc dot gnu.org 2022-02-21 13:04 ` jakub at gcc dot gnu.org 2022-02-22 9:43 ` cvs-commit at gcc dot gnu.org 2022-02-22 9:56 ` 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-104604-4-MdSO3AbgPD@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).