From: Rich Felker <dalias@libc.org>
To: Mike Granby <mikeg@mikeg.net>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [musl] sizeof(pthread_mutex_t) on aarch64
Date: Wed, 23 Aug 2023 16:04:41 -0400 [thread overview]
Message-ID: <20230823200440.GY4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <MN2PR12MB3087E376EA74F36F98A4EAE1AB1CA@MN2PR12MB3087.namprd12.prod.outlook.com>
On Wed, Aug 23, 2023 at 01:57:04PM +0000, Mike Granby wrote:
> Yeah, that all makes sense. I suspected that would be the case, but
> I figured I'd memorialize the issue in case someone else came across
> it. This way, they might at least find it via a search. Just for my
> interest, I'm going to have a quick look to figure out why glibc
> ends up with the different size on aarch64: It seems like it is the
> outlie, although my sample size is not large. Re gcompat, that
> didn't fix this particular issue and in any case, I really didn't
> like what it did to cmdline in procfs with its shimming, but I'll
> certainly keep an eye on its development. Thanks for the prompt
> response...
Re: gcompat, indeed at present it would not help at all, as all it
does is add some extra stuff not already in musl's internal
ABI-compat. Part of moving all the ABI-compat stuff to gcompat would
be getting rid of the need for the kind of shimming you don't like,
and having musl ldso do the work of loading a delegated ABI-compat
shared library for executables/modules that need it.
Rich
prev parent reply other threads:[~2023-08-23 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:09 Mike Granby
2023-08-23 13:29 ` Rich Felker
2023-08-23 13:57 ` Mike Granby
2023-08-23 20:04 ` Rich Felker [this message]
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=20230823200440.GY4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=mikeg@mikeg.net \
--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).