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 8B30A3858C3A; Thu,  9 May 2024 09:41:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8B30A3858C3A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715247704;
	bh=j36Okw7tR542LmUazaAxXUKDgUJzYZzEexGzvi3K3/I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ahLRRHI9dnkZ//aMr6XW+KjlRcDVQ3gTXosddOeBwn6tVfpmWZ7vNmwbtHdiNzz4a
	 8bzHNTL40YdOJhMBLs7SXZ++sWUfU9vQbCE04qqPPYTDgKbA6kXGwPQT9JuUCgI27w
	 ccBp8L3572VKH5Np8bEXZnbaRw7OKBMFZ0gvS9nY=
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113652] [14/15 regression] Failed bootstrap on ppc
 unrecognized opcode: `lfiwzx' with -mcpu=7450
Date: Thu, 09 May 2024 09:41:41 +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: 14.0
X-Bugzilla-Keywords: assemble-failure, build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113652-4-11z72WsEPY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113652-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=3D113652

--- Comment #26 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Michael Meissner from comment #23)
> 1) Ignore it and say to the users don't do that.
>=20
> 2) Prevent the IEEE 128-bit libgcc bits from being built on a BE or 32-bit
> LE system unless some configure switch is used.  Or just kick the can down
> the road, and don't provide a configure option in GCC 14, and if people a=
re
> interested do it in GCC 15.
>=20
> 3) Only build the IEEE 128-bit libgcc bits if the user configured the
> compiler with --with-cpu=3Dpower7, --with-cpu=3Dpower8, --with-cpu=3Dpowe=
r9,
> --with-cpu=3Dpower10 (and in the future --with-cpu=3Dpower11 or
> --with-cpu=3Dfuture).  This could be code that if __VSX__ is not defined,=
 the
> libgcc support functions won't get built.  We would then remove the -mvsx
> option from the library support functions.

4) Build those pieces of libgcc with the flags needed for that piece of cod=
e.
Like, just as is required for all other code.=