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/107704] [13 Regression] Testsuite regression after recent DCE changes
Date: Wed, 16 Nov 2022 12:37:04 +0000	[thread overview]
Message-ID: <bug-107704-4-j4QiJiV04m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107704-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107704

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization,
                   |                            |testsuite-fail
     Ever confirmed|0                           |1
   Target Milestone|---                         |13.0
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-11-16

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the only change is

   if (_11 == 0)
-    goto <bb 6>; [50.00%]
-  else
     goto <bb 9>; [50.00%]
-;;    succ:       6
-;;                9
+  else
+    goto <bb 6>; [50.00%]

;;   basic block 6, loop depth 0
;;    pred:       5
  goto <bb 9>; [100.00%]

that's which edge has the forwarder.  We are not good in preserving a
canonical form here and (repeated) CFG cleanup call yield either result
depending on which forwarder is removed first.

IIRC we've seen these kind of differences before.

An improvement here would be to enforce some processing order when
removing forwarders, like process EDGE_TRUE before EDGE_FALSE.  But even
that will inevitably cause issues like this bug.  A similar thing would
be enforcing that EDGE_TRUE is the first outgoing edge and EDGE_FALSE
the second.  But then this is more about visitation order and this part
of CFG cleanup just walks over all blocks in block order.

  parent reply	other threads:[~2022-11-16 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 16:45 [Bug target/107704] New: " law at gcc dot gnu.org
2022-11-15 16:46 ` [Bug target/107704] " law at gcc dot gnu.org
2022-11-16 12:37 ` rguenth at gcc dot gnu.org [this message]
2022-11-17  1:55 ` law at gcc dot gnu.org
2023-04-26  6:57 ` [Bug target/107704] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:24 ` rguenth at gcc dot gnu.org
2023-10-13  0:59 ` olegendo at gcc dot gnu.org
2024-05-21  9:12 ` [Bug target/107704] [13/14/15 " 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-107704-4-j4QiJiV04m@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: link
Be 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).