From: John David Anglin <dave@parisc-linux.org>
To: libc-alpha@sourceware.org
Cc: Helge Deller <deller@gmx.de>
Subject: [committed] hppa: Update struct __pthread_rwlock_arch_t comment
Date: Wed, 5 Apr 2023 18:59:27 +0000 [thread overview]
Message-ID: <ZC3FD3KUGZDn5sOZ@mx3210.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Committed to master.
Dave
---
hppa: Update struct __pthread_rwlock_arch_t comment.
Signed-off-by: John David Anglin <dave.anglin@bell.net>
diff --git a/sysdeps/hppa/nptl/bits/struct_rwlock.h b/sysdeps/hppa/nptl/bits/struct_rwlock.h
index 59bc9fe76f..762b05b2ec 100644
--- a/sysdeps/hppa/nptl/bits/struct_rwlock.h
+++ b/sysdeps/hppa/nptl/bits/struct_rwlock.h
@@ -27,11 +27,11 @@ struct __pthread_rwlock_arch_t
next four words are all set to 1 by the Linuxthreads
PTHREAD_RWLOCK_INITIALIZER. We ignore them in NPTL.
- The 16-byte aligned lock stucture causes various pthread
- structures to be over aligned. This causes some builds
- to fail which assume a maximum alignment of 8 bytes.
- Linuxthreads has been removed for 12 years, so drop
- alignment of lock structure. */
+ The 16-byte aligned lock stucture is not needed for NPTL.
+ It causes some package builds to fail (e.g., protobuf) and
+ issues with dynamic memory allocation in C++ versions prior
+ to C++17. Removing it allows for more efficient allocators
+ and better compatibility with other architectures. */
int __compat_padding[4];
unsigned int __readers;
unsigned int __writers;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2023-04-05 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZC3FD3KUGZDn5sOZ@mx3210.localdomain \
--to=dave@parisc-linux.org \
--cc=deller@gmx.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).