public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: John David Anglin <dave@parisc-linux.org>,
	deller@gmx.de, libc-alpha@sourceware.org
Subject: Re: [committed] hppa: Drop 16-byte pthread lock alignment
Date: Mon, 27 Mar 2023 01:37:28 +0100	[thread overview]
Message-ID: <87zg7zc9km.fsf@gentoo.org> (raw)
In-Reply-To: <87sfdrvxry.fsf@mid.deneb.enyo.de>

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]


Florian Weimer <fw@deneb.enyo.de> writes:

> * John David Anglin:
>
>> hppa: Drop 16-byte pthread lock alignment
>>
>> Linux threads were removed about 12 years ago and the current
>> nptl implementation only requires 4-byte alignment for pthread
>> locks.
>>
>> The 16-byte alignment causes various issues. For example in
>> building ignition-msgs, we have:
>>
>> /usr/include/google/protobuf/map.h:124:37: error: static assertion failed
>>   124 |   static_assert(alignof(value_type) <= 8, "");
>>       |                 ~~~~~~~~~~~~~~~~~~~~^~~~
>>
>> This is caused by the 16-byte pthread lock alignment.
>
> This was done deliberately to preserve ABI.  This change needs a mass
> rebuild because struct offsets after pthread_mutex_t members are
> likely to change.

On HPPA, I think we _may_ be fine with ABI breaks, but of course
we should use the proper mechanisms for that if we're doing it to
advertise it fully and allow distributions and users to prepare.

(We've done them before and there's not really any cache of binaries
that we need to keep compat. with anyway, it's more important to keep
things building usually.)

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  reply	other threads:[~2023-03-27  0:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 21:22 John David Anglin
2023-03-27  0:33 ` Florian Weimer
2023-03-27  0:37   ` Sam James [this message]
2023-03-27  1:58     ` John David Anglin
2023-03-27 12:42       ` Florian Weimer
2023-03-30 21:08         ` John David Anglin
2023-03-31  7:14           ` Florian Weimer
2023-03-27  0:35 ` Sam James
2023-03-27 15:24 ` Pedro Alves
2023-07-06 16:01 ` John David Anglin

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=87zg7zc9km.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=dave@parisc-linux.org \
    --cc=deller@gmx.de \
    --cc=fw@deneb.enyo.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).