public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106961] New: Testsuite failures after Command Line Tools update to v14
Date: Sat, 17 Sep 2022 14:59:50 +0000 [thread overview]
Message-ID: <bug-106961-4@http.gcc.gnu.org/bugzilla/> (raw)
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.
next reply other threads:[~2022-09-17 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 14:59 simon at pushface dot org [this message]
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
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@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).