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 bootstrap/111601] [14 Regression] profilebootstrap fails in stagestrain in libcody on x86_64-linux-gnu and powerpc64le-linux-gnu
Date: Mon, 27 Nov 2023 16:21:17 +0000 [thread overview]
Message-ID: <bug-111601-4-v87vMMjXsW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111601
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And under a debugger I can see exactly that happening. With the bad version of
splice_viable on the 16th call of splice_viable, I see
the code path in which r10 in the last hunk's spot where the addi r10,r10,96
from the second hunk was previously removed and the
0x0000000010424860 store changed into std r11,96(r10) from std r11,0(r10)
eventually reaches 0x0000000010424724 store which
consumed previously the store of r10 with 96 added to it but now just 0:
(gdb) disas 0x0000000010424860,0x0000000010424878
Dump of assembler code from 0x10424860 to 0x10424878:
0x0000000010424860 <_ZL13splice_viableP11z_candidatebPb+864>: std
r11,96(r10)
0x0000000010424864 <_ZL13splice_viableP11z_candidatebPb+868>: stb
r7,0(r5)
0x0000000010424868 <_ZL13splice_viableP11z_candidatebPb+872>: ori
r2,r2,0
0x000000001042486c <_ZL13splice_viableP11z_candidatebPb+876>: ld
r9,0(r8)
0x0000000010424870 <_ZL13splice_viableP11z_candidatebPb+880>: cmpdi
r9,0
0x0000000010424874 <_ZL13splice_viableP11z_candidatebPb+884>: bne
0x1042475c <_ZL13splice_viableP11z_candidatebPb+604>
End of assembler dump.
(gdb) disas 0x1042475c,0x0000000010424770
Dump of assembler code from 0x1042475c to 0x10424770:
0x000000001042475c <_ZL13splice_viableP11z_candidatebPb+604>: lwz
r7,104(r9)
0x0000000010424760 <_ZL13splice_viableP11z_candidatebPb+608>: li
r11,1
0x0000000010424764 <_ZL13splice_viableP11z_candidatebPb+612>: li
r29,1
0x0000000010424768 <_ZL13splice_viableP11z_candidatebPb+616>: cmpwi
r7,1
0x000000001042476c <_ZL13splice_viableP11z_candidatebPb+620>: b
0x104246fc <_ZL13splice_viableP11z_candidatebPb+508>
End of assembler dump.
(gdb) disas 0x104246fc,0x10424700
Dump of assembler code from 0x104246fc to 0x10424700:
0x00000000104246fc <_ZL13splice_viableP11z_candidatebPb+508>: beq
0x10424724 <_ZL13splice_viableP11z_candidatebPb+548>
End of assembler dump.
(gdb) disas 0x10424724,0x10424728
Dump of assembler code from 0x10424724 to 0x10424728:
=> 0x0000000010424724 <_ZL13splice_viableP11z_candidatebPb+548>: std
r9,0(r10)
End of assembler dump.
In the assembly, this corresponds to first jumping on non-equal to .L104 label,
then to .L54 label, and then immediately on non-equal to .L48 label.
next prev parent reply other threads:[~2023-11-27 16:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:27 [Bug bootstrap/111601] New: [14 Regression] bootstrap " doko at gcc dot gnu.org
2023-09-26 17:15 ` [Bug bootstrap/111601] " pinskia at gcc dot gnu.org
2023-10-17 2:11 ` bergner at gcc dot gnu.org
2023-10-18 13:31 ` doko at gcc dot gnu.org
2023-10-18 19:48 ` bergner at gcc dot gnu.org
2023-10-18 20:41 ` bergner at gcc dot gnu.org
2023-10-18 20:53 ` pinskia at gcc dot gnu.org
2023-10-18 21:26 ` bergner at gcc dot gnu.org
2023-10-19 6:23 ` rguenth at gcc dot gnu.org
2023-11-17 5:33 ` jeevitha at gcc dot gnu.org
2023-11-24 19:59 ` jakub at gcc dot gnu.org
2023-11-26 21:36 ` [Bug bootstrap/111601] [14 Regression] profilebootstrap " jakub at gcc dot gnu.org
2023-11-27 11:37 ` jakub at gcc dot gnu.org
2023-11-27 12:24 ` rguenther at suse dot de
2023-11-27 12:27 ` jakub at gcc dot gnu.org
2023-11-27 13:31 ` jakub at gcc dot gnu.org
2023-11-27 13:51 ` jakub at gcc dot gnu.org
2023-11-27 15:14 ` jakub at gcc dot gnu.org
2023-11-27 16:21 ` jakub at gcc dot gnu.org [this message]
2023-11-27 16:45 ` jakub at gcc dot gnu.org
2023-11-27 16:57 ` jakub at gcc dot gnu.org
2023-11-27 17:01 ` jakub at gcc dot gnu.org
2023-11-27 18:33 ` jakub at gcc dot gnu.org
2023-11-27 19:24 ` jakub at gcc dot gnu.org
2023-11-27 20:02 ` jakub at gcc dot gnu.org
2023-11-27 20:17 ` jakub at gcc dot gnu.org
2023-11-29 8:18 ` cvs-commit at gcc dot gnu.org
2023-11-29 8:31 ` jakub at gcc dot gnu.org
2023-11-30 17:20 ` jeevitha 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-111601-4-v87vMMjXsW@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).