public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104982] [12 Regression] FAIL: gcc.target/i386/bt-5.c by r12-7687 Date: Mon, 21 Mar 2022 08:52:37 +0000 [thread overview] Message-ID: <bug-104982-4-dCBamJGzRt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104982-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104982 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-*-* i?86-*-* Ever confirmed|0 |1 Last reconfirmed| |2022-03-21 Status|UNCONFIRMED |NEW Keywords| |missed-optimization Target Milestone|--- |12.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. From my analysis at the point I pushed the offending revision the edges out of a conditional are now swapped, EDGE_SUCC (bb, 1) vs. EDGE_SUCC (bb, 0), and that somehow leads to magic no longer happening. That's of course a condition (the particular edge order) that we can't rely on. If there's a "better" one for expanding RTL we should conciously choose it there.
next prev parent reply other threads:[~2022-03-21 8:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-18 22:25 [Bug target/104982] New: " hjl.tools at gmail dot com 2022-03-21 8:52 ` rguenth at gcc dot gnu.org [this message] 2022-03-21 9:10 ` [Bug target/104982] " crazylht at gmail dot com 2022-03-21 9:16 ` crazylht at gmail dot com 2022-03-21 9:45 ` crazylht at gmail dot com 2022-03-21 9:49 ` rguenth at gcc dot gnu.org 2022-03-22 8:31 ` cvs-commit at gcc dot gnu.org 2022-03-22 8:33 ` crazylht at gmail dot com 2022-03-22 8:46 ` 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-104982-4-dCBamJGzRt@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).