public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/96404] [10 Regression] Bootstrap failure
Date: Sun, 02 Aug 2020 00:34:21 +0000 [thread overview]
Message-ID: <bug-96404-4-c1gCBCqTam@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96404-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96404
--- Comment #13 from David Edelsohn <dje at gcc dot gnu.org> ---
The symptom I see on AIX is that the labels for DWARF variable locations differ
between stage2 and stage3 for some files. The difference started with the
recent change to the var-tracking pass. Once the labels diverge, the addresses
no longer match and the object file differ.
The var-tracking dump files are over 1GB with lots of address differences, but
it doesn't contain any differences in the BB dump output for vt_find_locations,
which is the function that was changed.
The assembly file differences give the appearance of an unstable sort. The
beginning of the difference for an assembly file looks like:
--- tree-vrp.S 2020-08-01 19:42:00.000000000 -0400
+++ ../gcc/tree-vrp.S 2020-08-01 19:43:33.000000000 -0400
@@ -38428,8 +38428,8 @@
LM..7111:
addi 19,1,792
li 20,1
-L..2070:
LVL..2903:
+L..2070:
LBE..22006:
LBE..22005:
LBE..22004:
@@ -38466,6 +38466,7 @@
LM..7114:
cmpwi 0,31,0
beq 0,L..2043
+LVL..2904:
LBB..22481:
LM..7115:
LM..7116:
@@ -38475,12 +38476,12 @@
mr 30,31
bl .memcpy
nop
-LVL..2904:
+LVL..2905:
LM..7117:
LM..7118:
LM..7119:
lwz 27,8(31)
-LVL..2905:
+LVL..2906:
LM..7120:
LM..7121:
lwz 9,4(27)
@@ -38489,7 +38490,7 @@
beq 0,L..2348
L..2044:
LM..7123:
-LVL..2906:
+LVL..2907:
LBE..22481:
LBE..22508:
LBE..22535:
next prev parent reply other threads:[~2020-08-02 0:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 17:43 [Bug bootstrap/96404] New: [10 Regression] AIX Bootstrap failure with DWARF debug changes dje at gcc dot gnu.org
2020-07-31 17:44 ` [Bug bootstrap/96404] " dje at gcc dot gnu.org
2020-07-31 21:05 ` slyfox at gcc dot gnu.org
2020-07-31 21:06 ` slyfox at gcc dot gnu.org
2020-07-31 21:06 ` dje at gcc dot gnu.org
2020-07-31 21:07 ` dje at gcc dot gnu.org
2020-07-31 21:13 ` [Bug bootstrap/96404] [10 Regression] Bootstrap failure slyfox at gcc dot gnu.org
2020-07-31 21:16 ` dje at gcc dot gnu.org
2020-07-31 21:17 ` dje at gcc dot gnu.org
2020-07-31 21:25 ` slyfox at gcc dot gnu.org
2020-07-31 21:32 ` slyfox at gcc dot gnu.org
2020-08-01 1:02 ` dje at gcc dot gnu.org
2020-08-01 11:34 ` dje at gcc dot gnu.org
2020-08-01 15:56 ` dje at gcc dot gnu.org
2020-08-02 0:34 ` dje at gcc dot gnu.org [this message]
2020-08-02 7:53 ` slyfox at gcc dot gnu.org
2020-08-02 10:56 ` slyfox at gcc dot gnu.org
2020-08-02 12:42 ` slyfox at gcc dot gnu.org
2020-08-02 16:45 ` dje at gcc dot gnu.org
2020-08-02 18:37 ` cvs-commit at gcc dot gnu.org
2020-08-02 18:42 ` [Bug bootstrap/96404] [11 " slyfox at gcc dot gnu.org
2020-08-03 7:00 ` 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-96404-4-c1gCBCqTam@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).