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 66307385DC02; Sat, 11 Apr 2020 01:41:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 66307385DC02
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1586569296;
 bh=HfqMALCPzDYEfE4gujGZ1wwOAWvee+gZakQZJnqMppk=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=vx9cphkt5YDBvJDeCxWdtQXPFq3jcqKrrWc7giLLwdWZNOtQa89v7Rxlo4UMO+wjL
 vCYcq5Z1oH70xkE8QuWejHpzoKUV186fpXt5xVeEwSiY0rz+DPyvI8hnpaoagJ4u5p
 1pqIoEfIrUq1+04YMAEXHEnUURZPIEkGmbhAxS7E=
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/87252] gcc-4.4 cross-builds broken, apparently in
 self-tests
Date: Sat, 11 Apr 2020 01:41:36 +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: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-87252-4-6gYfhUP8fV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87252-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87252-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Apr 2020 01:41:36 -0000

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

--- Comment #10 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Abrahm Scully from comment #9)
> Either way, building gcc-4.7.4 first and then building gcc-10 with that
> produces a compiler without the problem.
>=20
> Again, sorry for the noise.

Please, do *not* apologize.  Even if you'd just repeat other observations, =
your
observations would serve as a confirmation.  But they're also new AFAICT.

So, your recent observation is that gcc-4.7.4 apparently works here.  Looki=
ng
deeper into what construct is used in the self-tests, that started working =
with
that version would likely help, if someone is so inclined.

Or, maybe it'd be ok to just disable the self-testing code before that vers=
ion.
 Alternatively, plain raising the base version of the gcc being supported f=
or
gcc *development* to 4.7.4 would probably be acceptable too.  To newcomers:
remember, this is just the cross-gcc case.=