public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113986] [14 regression] Build failure on aarch64-linux-musl (error: 'export_load_16' aliased to undefined symbol 'libat_load_16')
Date: Mon, 19 Feb 2024 05:19:06 +0000 [thread overview]
Message-ID: <bug-113986-4-DjgMxZA8Pd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113986-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-02-19
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I am 99% sure it was caused by r14-6589-g3fa689f6ed8387 .
It is reproducible with --disable-gnu-indirect-function on the gcc configure
line for a glibc build even without the patch for PR 113971 so confirmed.
Moving the definition of DONE for N==16 case to be under the `#if HAVE_IFUNC`
case fixes the issue. I don't know if that is the correct fix or not ...
next prev parent reply other threads:[~2024-02-19 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 4:47 [Bug target/113986] New: " sjames at gcc dot gnu.org
2024-02-19 4:51 ` [Bug target/113986] " pinskia at gcc dot gnu.org
2024-02-19 5:19 ` pinskia at gcc dot gnu.org [this message]
2024-02-19 22:41 ` [Bug target/113986] [14 regression] Build failure on aarch64-linux-musl or if ifunc support is disabled " wilco at gcc dot gnu.org
2024-02-19 22:46 ` pinskia at gcc dot gnu.org
2024-02-23 16:41 ` wilco at gcc dot gnu.org
2024-02-25 15:43 ` sjames at gcc dot gnu.org
2024-03-27 3:11 ` raj.khem at gmail dot com
2024-04-04 21:29 ` cvs-commit at gcc dot gnu.org
2024-04-08 12:15 ` wilco 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-113986-4-DjgMxZA8Pd@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).