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 13:51:41 +0000	[thread overview]
Message-ID: <bug-111601-4-0on5dPoOO5@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 #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Looking at the assembly difference, I see just a few functions:
--- cp/call.s2  2023-11-27 13:40:15.088908624 +0000
+++ cp/call.s1  2023-11-27 13:35:56.912298399 +0000
@@ -364,13 +364,12 @@ _ZL13splice_viableP11z_candidatebPb:
        std 9,0(10)
        mr 10,9
        li 11,0
-       addi 10,10,96
        li 7,1
        addi 6,6,1
        addi 12,12,1
        ld 9,96(9)
        std 9,0(8)
-       std 11,0(10)
+       std 11,96(10)
        stb 7,0(5)
        ori 2,2,0
        ld 9,0(8)
@@ -449,10 +448,9 @@ _ZL13splice_viableP11z_candidatebPb:
        .cfi_restore 25
        std 9,0(10)
        mr 10,9
-       addi 10,10,96
        li 26,0
-       ld 7,.LANCHOR0+136@toc@l(11)
        li 28,0
+       ld 7,.LANCHOR0+136@toc@l(11)
        addi 6,6,1
        addi 12,12,1
        addi 7,7,1
@@ -461,8 +459,9 @@ _ZL13splice_viableP11z_candidatebPb:
        li 11,0
        li 7,1
        std 9,0(8)
-       std 11,0(10)
+       std 11,96(10)
        stb 7,0(5)
+       ori 2,2,0
        ld 9,0(8)
        cmpdi 0,9,0
        bne 0,.L104
@@ -21377,24 +21376,22 @@ _ZN2wi5lts_pI16generic_wide_intINS_13ext
        nop
        addis 10,2,.LANCHOR0+5848@toc@ha
        mr 5,30
-       addi 29,1,64
        ld 9,.LANCHOR0+5848@toc@l(10)
-       std 3,0(29)
+       std 3,64(1)
        addi 3,1,48
-       std 4,8(29)
+       std 4,72(1)
        lis 4,0x2
        addi 9,9,1
        std 9,.LANCHOR0+5848@toc@l(10)
        bl
_ZN2wi10int_traitsI16generic_wide_intINS_13extended_treeILi131072EEEEE9decomposeEPljRKS4_
        nop
-       addi 9,1,32
        lwz 30,72(1)
        ld 29,64(1)
        rldicl 7,4,0,32
+       std 3,32(1)
+       std 4,40(1)
        mr 6,3
        cmplwi 0,7,1
-       std 3,0(9)
-       std 4,8(9)
        beq 0,.L2422
        addis 10,2,.LANCHOR0+5912@toc@ha
        rldicl 4,30,0,32
@@ -51700,10 +51697,9 @@ _ZL8op_errorRK13op_location_t9tree_codeS
        addis 7,2,.LC1285@toc@ha
        ld 7,.LC1285@toc@l(7)
        lbzx 10,10,5
-       addi 10,10,58
        sldi 10,10,5
        add 10,7,10
-       ld 29,8(10)
+       ld 29,1864(10)
 .L6276:
        cmpdi 0,30,0
        beq 0,.L6338
@@ -172014,7 +172010,7 @@ __gcov7._Z15good_conversionP9tree_nodeS0
        .long   1110716448
        .zero   4
        .quad   0
-       .long   285183267
+       .long   284929938
        .long   1725772321
        .quad   .LC2647
        .quad   __gcov_merge_add
While most of the changes look reasonable (but I haven't so far verified if the
removed additions turned into memory immediates set registers which aren't used
in other places),
the addition of ori 2,2,0 instruction seems kind of unexpected.

  parent reply	other threads:[~2023-11-27 13:51 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 [this message]
2023-11-27 15:14 ` jakub at gcc dot gnu.org
2023-11-27 16:21 ` jakub at gcc dot gnu.org
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-0on5dPoOO5@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).