From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6DA443858004; Mon, 27 Nov 2023 15:14:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6DA443858004
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701098098;
	bh=EBCmnoBu+D3txZ+pa50mL4rzmu+7a6LC3LHtCUM27T0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=LvQDnoeTLHGqKdLAQ/IMWK+ntYUFuKZsZ8d79+KJa9es2g1Q8F6VFJ9tiuNHLZQN7
	 nDbmJhFVLBt8W/rMc645AGu+8n6sL1AN1eXtGm3a/x/ZqoEQeGbXUFdoqiaRLTXbwJ
	 bwiaDRoAorpGNwccp+MSi9sHytoXC6lGkPU5rYqA=
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 15:14:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: build, ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111601-4-QxQ8SKaSHJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111601-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111601-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
oris 2,2,0 is a noop group_ending_nop.
Anyway, that oris 2,2,0 nor the li 28, 0 scheduling don't change anything a=
nd
I've
narrowed it down (- bad, + working) to the
--- cp/call.s   2023-11-27 14:24:12.616613833 +0000
+++ cp/call.s   2023-11-27 15:08:47.345457528 +0000
@@ -364,12 +364,13 @@ _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,96(10)
+       std 11,0(10)
        stb 7,0(5)
        ori 2,2,0
        ld 9,0(8)
@@ -448,6 +449,7 @@ _ZL13splice_viableP11z_candidatebPb:
        .cfi_restore 25
        std 9,0(10)
        mr 10,9
+       addi 10,10,96
        li 26,0
        li 28,0
        ld 7,.LANCHOR0+136@toc@l(11)
@@ -459,7 +461,7 @@ _ZL13splice_viableP11z_candidatebPb:
        li 11,0
        li 7,1
        std 9,0(8)
-       std 11,96(10)
+       std 11,0(10)
        stb 7,0(5)
        ori 2,2,0
        ld 9,0(8)
changes so far.  So I bet 10 must be somewhere live after those stores.
Reverting further either the first or second two hunks breaks it again.=