From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Carlos O'Donell <carlos@redhat.com>,
libc-alpha@sourceware.org, glaubitz@physik.fu-berlin.de
Subject: Re: [PATCH] m68: Enforce 4-byte alignment on internal locks (BZ #29537)
Date: Tue, 30 Aug 2022 11:23:25 -0300 [thread overview]
Message-ID: <85a010fe-e2a8-56bb-68d0-fec449cec164@linaro.org> (raw)
In-Reply-To: <933ac04b-5d33-c482-67a6-ce176f3170a7@redhat.com>
On 30/08/22 11:18, Carlos O'Donell wrote:
> On 8/30/22 09:35, Adhemerval Zanella via Libc-alpha wrote:
>> The HPPA also requires a 16-byte alignment for locks, although it is
>> just a historical artifact to keep compatibility with old
>> implementation.
>> ---
>> sysdeps/nptl/libc-lockP.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/sysdeps/nptl/libc-lockP.h b/sysdeps/nptl/libc-lockP.h
>> index d3a6837fd2..9efe962588 100644
>> --- a/sysdeps/nptl/libc-lockP.h
>> +++ b/sysdeps/nptl/libc-lockP.h
>> @@ -34,7 +34,7 @@
>> #include <tls.h>
>>
>> /* Mutex type. */
>> -typedef int __libc_lock_t;
>> +typedef int __libc_lock_t __LOCK_ALIGNMENT;
>> typedef struct { pthread_mutex_t mutex; } __rtld_lock_recursive_t;
>> typedef pthread_rwlock_t __libc_rwlock_t;
>
> Are you able to verify that this doesn't change the ABI of any other
> structures that might have an internal lock?
>
> Normally I would use libabigail[1] before and after the patch to look
> for subtype size changes in public ABIs/APIs.
>
It should not and I would consider this an bug since the header is internal
only and all definitions are used solely on internal code (although
pthreadtypes-arch.h is an installed header, libc-lockP.h is not).
next prev parent reply other threads:[~2022-08-30 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 13:35 Adhemerval Zanella
2022-08-30 13:46 ` John Paul Adrian Glaubitz
2022-08-30 13:54 ` Adhemerval Zanella Netto
2022-08-30 14:18 ` Carlos O'Donell
2022-08-30 14:23 ` Adhemerval Zanella Netto [this message]
2022-08-30 16:32 ` Richard Henderson
2022-08-30 17:04 ` Adhemerval Zanella Netto
2022-09-02 17:29 ` Andreas K. Huettel
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=85a010fe-e2a8-56bb-68d0-fec449cec164@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=libc-alpha@sourceware.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).