public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-106961-4-OWlNg0GEYE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106961-4@http.gcc.gnu.org/bugzilla/>

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

--- 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 GCC,
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.

  parent reply	other threads:[~2022-09-20  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 14:59 [Bug target/106961] New: " simon at pushface dot org
2022-09-17 15:18 ` [Bug target/106961] " pinskia at gcc dot gnu.org
2022-09-18  8:43 ` simon at pushface dot org
2022-09-20  9:24 ` simon at pushface dot org
2022-09-20  9:36 ` iains at gcc dot gnu.org [this message]
2022-09-20 17:43 ` simon at pushface dot org
2022-09-28 10:23 ` simon at pushface dot org
2022-09-28 11:24 ` iains at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106961-4-OWlNg0GEYE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).