[Bug target/106961] New: Testsuite failures after Command Line Tools update to v14

[Bug target/106961] New: Testsuite failures after Command Line Tools update to v14

[simon at pushface dot org]

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

            Bug ID: 106961
           Summary: Testsuite failures after Command Line Tools update to
                    v14
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: simon at pushface dot org
  Target Milestone: ---

On re-running 'make check-acats', I got 37 fails (can’t remember what the count
was before the change that triggered this, think it was zero) of which 19
included this text, sometimes once, sometimes multiple times:

   libunwind: _Unwind_GetTextRelBase - _Unwind_GetTextRelBase() not implemented

This appears to have been caused by Apple’s release of the Command Line Tools
version 14.

I get very similar results on aarch64-apple-darwin21. On that architecture, the
log for 'make check-g++` contains the text listed above.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[pinskia at gcc dot gnu.org]

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Sounds like you should report this to Apple ...

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[simon at pushface dot org]

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

--- Comment #2 from simon at pushface dot org ---
For the moment, installing Command Line Tools version 13(.4) fixes this problem
(people using Xcode need to revert that).

I guess the long-term solution will depend on whether the missing libunwind
component is deliberate or an oversight on Apple’s part.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[simon at pushface dot org]

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

--- Comment #3 from simon at pushface dot org ---
Problem still present in Xcode 4.1beta.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[iains at gcc dot gnu.org]

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.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[simon at pushface dot org]

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

--- Comment #5 from simon at pushface dot org ---
I used the feedback app to submit FB11552589; as a first-timer I’m unsure
whether I’ve done it right.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[simon at pushface dot org]

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

--- Comment #6 from simon at pushface dot org ---
Installing the Command Line Tools 14.1 beta 3 fixes this problem.

[Bug target/106961] Testsuite failures after Command Line Tools update to v14

[iains at gcc dot gnu.org]

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

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
closing as invalid - because it is not a GCC bug, and now we have a newer CLT
that works.