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 8D25E3858C2D; Mon, 27 Nov 2023 20:17:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8D25E3858C2D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701116266;
	bh=cP+2a1hTTKFQY/GuN5TTQOZrFhF4JWwdZPE/gbIxzeA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=t1EBZWVjO70TkaLKozv9b04e+mRcYnvOe0iQmZdUZ91F7wjuqD06KhLd6LwFcW4Zb
	 HO6h4P/RlsNm5PhI/ApsMqpdvzWRdvfyLqM07fmQt827mrZeA0TMGcOo2zjqyR/qNV
	 kpGgek9L2aD90OClIrzHwm/MX+z0Pmj5SapkJJ54=
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 20:17:46 +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
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-U3MxeQZlkp@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 #24 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As the pass seems to work on one basic block at the time (everything from
analysis to actual changes), I wonder if e.g. get_uses shouldn't punt if it
sees (non-DEBUG_INSN!) uses in other basic block but the current one (this
would still not fix this wrong-code) or if the definition's luid is higher =
than
use's luid (i.e. the use is in the same bb, but still from a different
iteration of the loop).
See the
          loop:
          *last_viable =3D c;
          *cand =3D c->next;
          c->next =3D (z_candidate *) 0;
          last_viable =3D &c->next;
          if (!*cand)
            break;
          c =3D *cand;
          goto loop;
statements done in the loop body, the *last_viable =3D c; store is the %r9 =
store
to %r10
(which is initially address of some automatic variable, but &c->next aka c =
+ 96
for second and following iteration), the c->next =3D 0 store is the %r5 sto=
re to
%r10 (which has been incremented by 96 first.=