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 80FD83858CDB; Wed,  1 Mar 2023 13:45:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 80FD83858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677678350;
	bh=6tsDWc2W2eE08knhcdjZjClQWvTHjszp/6K+Da+pT4U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JIcWA7RB4i3FCBZHeyiQPQ0hMk63IMy7c4VyEf3AuyNssUuyjqvvP+ZYMwyhI4N6a
	 ZbOCRT6GJtD/Xgjst2eOyC2W9FaRN/IqjsafNr06Xpltg5D4sSaz2vRzFvS4eTXBuq
	 as/b7tpUO3aLOc3pnbcTAOESi9lG/2PKwFYY4SJ8=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108984] [13 Regression] LTO bootstrap causes testsuite
 ICE
Date: Wed, 01 Mar 2023 13:45:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108984-4-XpglFzyGjV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108984-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=3D108984

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Isn't what happens in i386.cc more like:
void foo (long);
int data[128];
static int bar (int i, long j)
{
  if (j >=3D -64 && j <=3D 64)
    return data[j+64];
  foo (j);
}

int baz (unsigned int j)
{
  int k =3D j / 8;
  return bar (0, -k);
}
?  Because we know in the caller it is [-0x1fffffff, 0] ...=