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 debug/105627] -fcompare-debug failure at -Og for powerpc64le-unknown-linux-gnu
Date: Wed, 18 May 2022 14:53:51 +0000	[thread overview]
Message-ID: <bug-105627-4-uK0RxVWmVq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105627-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-05-18
             Status|UNCONFIRMED                 |NEW
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |linkw at gcc dot gnu.org,
                   |                            |segher at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This diverges in the swaps rs6000-specific pass.
With:
-Og -fcompare-debug pr105627.c -fdump-tree-all -da --param
min-nondebug-insn-uid=10000
one can see:
@@ -173,17 +173,17 @@ Relevant insns with their flag settings
  10359  10355  store swappable special:store 
  10360  10356  store swappable special:store 
  10361  10357  store swappable special:store 
- 10363      0  load swap 
+ 10363  10371  load swap 
  10364  10363  swap 
  10365  10363  swappable 
  10366  10363  swap 
  10367  10363  store swap 
- 10371      0  load swap 
+ 10371  10379  load swap 
  10372  10371  swap 
  10373  10371  swappable 
  10374  10371  swap 
  10375  10371  store swap 
- 10379      0  load swap 
+ 10379  10387  load swap 
  10380  10379  swap 
  10381  10379  swappable 
  10382  10379  swap 
...
@@ -456,18 +456,6 @@ deferring rescan insn with uid = 10415.
 Replacing store 10415 with permuted store
 deferring rescan insn with uid = 10416.
 Replacing store 10416 with permuted store
-deferring rescan insn with uid = 10432.
-deferring rescan insn with uid = 10432.
-Replacing swap 10018 with copy 10432
-deferring deletion of insn with uid = 10018.
-deferring rescan insn with uid = 10433.
-deferring rescan insn with uid = 10433.
-Replacing swap 10364 with copy 10433
-deferring deletion of insn with uid = 10364.
-deferring rescan insn with uid = 10434.
-deferring rescan insn with uid = 10434.
-Replacing swap 10366 with copy 10434
-deferring deletion of insn with uid = 10366.
 starting the processing of deferred insns
 verify found no changes in insn with uid = 10354.
 verify found no changes in insn with uid = 10355.
etc. changes.  DEBUG_INSNs shouldn't influence optimization decisions, but of
course might need to be adjusted or reset in some cases.

  reply	other threads:[~2022-05-18 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 12:19 [Bug debug/105627] New: " zsojka at seznam dot cz
2022-05-18 14:53 ` jakub at gcc dot gnu.org [this message]
2022-05-19  7:28 ` [Bug debug/105627] " linkw at gcc dot gnu.org
2022-05-24  6:08 ` cvs-commit at gcc dot gnu.org
2022-05-24  6:22 ` linkw at gcc dot gnu.org
2022-10-27  2:25 ` [Bug target/105627] " 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-105627-4-uK0RxVWmVq@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).