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 C44533858C55; Tue, 20 Sep 2022 09:36:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C44533858C55
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663666591;
	bh=k7IvlpWtzSCD9gsBMJjjUTygqXkANX+q2YeB9SecA8c=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=C1KGM9zY40SSC9/loLeW82BtY99MCwqIWyH9EVBSJi8F5zNQ6VW4wKWwGjsU2koPm
	 dKNvNiRLRgFZFsVEpQ6/dviRkTmWSVGaEQ0Mt+ko91ar30omeSqsJObbmzNn95iw0M
	 32tx3NduS8yOFGpzx6ebRRVfNlLqRfT/gs14U7Cg=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106961] Testsuite failures after Command Line Tools
 update to v14
Date: Tue, 20 Sep 2022 09:36:30 +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: 12.1.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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-106961-4-OWlNg0GEYE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106961-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=3D106961

--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to simon from comment #3)
> Problem still present in Xcode 4.1beta.

>From a GCC perspective, what's needed is:

 * for someone to file a radar with Apple ("feedback" they are called now)
[https://feedbackassistant.apple.com]

 * If it is acknowledged as an Xcode bug, and we have no way to work around=
 it,
then  we will just need to document that certain versions of Xcode are not
usable.

 * If the outcome of the FB is that the problem is determined to be with GC=
C,
then we will have to address it.

As of now, it's not clear to me that this is a GCC bug - removing a symbol =
from
the library looks like an ABI break.=