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 6BE923885508; Wed, 26 Oct 2022 19:32:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6BE923885508
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666812737;
	bh=8mBf08hWb7Cn+KH0AWkmz8QZ3VXXcMkoLKSnQycbtGs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ybpYb4vK2KX6rwxWDtEitnuplbhqE8OkHq0Xy2Uxduwh1DhC8aA2a/dipI/WdZbXY
	 Mn4euVzc1eC//iKwPuh6uOWA1Lz/b+PlaGwwCe1ISwu0F+BJoQlxQEsf9wL1g2mhUp
	 maZ0knzzlpkWRVDsgkXxEXRdbDOHDH+1MJdRDFss=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93177] PPC: Missing many useful platform intrinsics
Date: Wed, 26 Oct 2022 19:32:16 +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: 8.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-93177-4-CZcKS4LwA4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93177-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93177-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=3D93177

--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #18)
> (In reply to Sergey Fedorov from comment #16)
> > For Darwin, PPC intrinsics already is there in Apple headers. Can it be
> > added into current GCC?
>=20
> If it is in the Apple headers already, why would you need a separate copy
> in GCC?

it's an internal header in apple-gcc-4.x so not accessible to end users unl=
ess
using those compiles (nor usable like <altivec.h> by GCC for example).

Some projects appear to depend on it (whether broken or not)...
.. but I'd welcome some persuasive evidence that it does make things better=
.=