From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] make __getauxval a public ABI symbol
Date: Mon, 6 Nov 2023 13:49:33 -0500 [thread overview]
Message-ID: <20231106184933.GU4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20231012183148.GD1427497@port70.net>
On Thu, Oct 12, 2023 at 08:31:48PM +0200, Szabolcs Nagy wrote:
> This is needed so that libgcc can access AT_HWCAP without violating
> link namespace rules.
>
> Internally musl already used __getauxval symbol for the same reason,
> we just remove the hidden marking.
>
> Currently libgcc only uses __getauxval on aarch64 for outline atomics
> and only on glibc, but there is plan to add more usage (this time in
> the unwinder) which may cause link failure on musl in the future.
> (libgcc cannot easily check for libc symbols due to bootstrap order,
> the feature could be unconditionally disabled for *-linux-musl, but
> it's probably more future proof to provide the symbol.)
> ---
> src/include/sys/auxv.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/include/sys/auxv.h b/src/include/sys/auxv.h
> index 9358a4a5..63c5bfe9 100644
> --- a/src/include/sys/auxv.h
> +++ b/src/include/sys/auxv.h
> @@ -5,6 +5,6 @@
>
> #include <features.h>
>
> -hidden unsigned long __getauxval(unsigned long);
> +unsigned long __getauxval(unsigned long);
>
> #endif
> --
> 2.41.0
This is probably okay. Are error/errno semantics expected to be the
same as the public getauxval? IIRC this was a topic of confusion at
one point in the past.
Rich
next prev parent reply other threads:[~2023-11-06 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 18:31 Szabolcs Nagy
2023-11-06 18:49 ` Rich Felker [this message]
2023-11-06 21:51 ` Szabolcs Nagy
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=20231106184933.GU4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).