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/108166] [12/13 Regression] Wrong code with -O2 Date: Sun, 18 Dec 2022 21:08:00 +0000 [thread overview] Message-ID: <bug-108166-4-ctXaMhgPCN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108166-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108166 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.3 Last reconfirmed| |2022-12-18 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. # iftmp.2_17 = PHI <iftmp.2_24(5), 0(4)> if (iftmp.2_17 != 0) goto <bb 8>; [INV] else goto <bb 7>; [INV] <bb 7> : <bb 8> : # iftmp.1_16 = PHI <iftmp.2_17(6), 8(7)> _7 = _4 > iftmp.1_16; _8 = (int) _7; c = _8; D.3392 ={v} {CLOBBER(eol)}; D.3393 ={v} {CLOBBER(eol)}; _11 = iftmp.2_17 != 0; And then _11 gets replaced with: _6 = iftmp.2_10 != 0; I can't figure out why though.
next prev parent reply other threads:[~2022-12-18 21:08 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-18 19:46 [Bug tree-optimization/108166] New: " vsevolod.livinskiy at gmail dot com 2022-12-18 21:08 ` pinskia at gcc dot gnu.org [this message] 2022-12-19 8:17 ` [Bug tree-optimization/108166] " rguenth at gcc dot gnu.org 2022-12-19 8:34 ` [Bug tree-optimization/108166] [12/13 Regression] Wrong code with -O2 since r12-8078-ga42aa68bf1ad745a marxin at gcc dot gnu.org 2022-12-19 13:13 ` jakub at gcc dot gnu.org 2022-12-21 12:52 ` jakub at gcc dot gnu.org 2022-12-21 13:12 ` rguenth at gcc dot gnu.org 2022-12-21 13:14 ` rguenth at gcc dot gnu.org 2022-12-21 13:35 ` jakub at gcc dot gnu.org 2022-12-22 11:53 ` cvs-commit at gcc dot gnu.org 2022-12-22 11:55 ` [Bug tree-optimization/108166] [12 " jakub at gcc dot gnu.org 2023-02-10 17:45 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:59 ` jakub at gcc dot gnu.org 2024-02-01 22:16 ` pinskia 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-108166-4-ctXaMhgPCN@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).