From: Bruno Haible <bruno@clisp.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
bug-gettext@gnu.org
Subject: Re: building GNU gettext on AIX
Date: Fri, 17 Nov 2023 01:07:01 +0100 [thread overview]
Message-ID: <5798081.UuxTggG6dJ@nimes> (raw)
In-Reply-To: <CAGWvny=PdsxHjBXCgBmJF0HWvUkW2Y=2-gEKkbEeSWuAoXYtWg@mail.gmail.com>
David Edelsohn wrote:
> > ibm-clang links against libpthread.a as well:
> > $ ldd /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig
> > /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig needs:
> > /usr/lib/libpthreads.a(shr_xpg5_64.o)
> > /usr/opt/zlibNX/lib/libz.a(libz.so.1)
> > /usr/lib/libcurses.a(shr42_64.o)
> > /usr/lib/libiconv.a(shr4_64.o)
> > /usr/lib/libc++.a(shr_64.o)
> > /usr/lib/libc++abi.a(libc++abi.so.1)
> > /usr/lib/libc.a(shr_64.o)
> > /usr/lib/libpthreads.a(_shr_xpg5_64.o)
> > /usr/lib/libc++.a(libc++.so.1)
> > /usr/lib/libunwind.a(libunwind.so.1)
> > /usr/lib/libc.a(_shr_64.o)
> > /unix
> > /usr/lib/libcrypt.a(shr_64.o)
> >
>
> I have asked the IBM Clang team why ibm-clang depends on libpthreads.
The reason is that
- For a library, it is a normal expectation nowadays that it is
multithread-safe.
- Making a library multithread-safe (without major hacks) means to do
locking or to call pthread_once / call_once in some places.
- The ISO C 11 threading functions in libc have some drawbacks compared
to the pthread functions. [1] So most developer prefer to rely on the
POSIX threads API.
- Since AIX does not have the POSIX mutex functions in libc and does not
support weak symbols like in ELF, this means a dependency to
pthread_mutex_lock or pthread_once.
- Accordingly, in the list of libraries above, 3 libraries need pthread*
symbols:
$ nm -X 64 /usr/lib/libc++abi.a | grep ' U ' | grep pthread_mutex
pthread_mutex_lock U -
pthread_mutex_unlock U -
$ nm -X 64 /usr/lib/libc++.a | grep ' U ' | grep pthread_mutex
pthread_mutex_destroy U -
pthread_mutex_init U -
pthread_mutex_lock U -
pthread_mutex_trylock U -
pthread_mutex_unlock U -
pthread_mutexattr_destroy U -
pthread_mutexattr_init U -
pthread_mutexattr_settype U -
$ nm -X 64 /usr/opt/zlibNX/lib/libz.a | grep ' U ' | grep pthread_mutex
pthread_mutex_destroy U -
pthread_mutex_init U -
pthread_mutex_lock U -
pthread_mutex_unlock U -
Bruno
[1] Lock initialization is clumsy. The return value of a thread is only an
'int', not a pointer. Etc.
next prev parent reply other threads:[~2023-11-17 0:07 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 20:37 [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext David Edelsohn
2023-11-14 23:06 ` Arsen Arsenović
2023-11-15 1:49 ` David Edelsohn
2023-11-15 12:29 ` building GNU gettext on AIX Bruno Haible
2023-11-15 19:26 ` David Edelsohn
2023-11-15 21:22 ` Bruno Haible
2023-11-15 21:31 ` David Edelsohn
2023-11-15 22:39 ` Bruno Haible
2023-11-16 16:00 ` David Edelsohn
2023-11-16 16:35 ` David Edelsohn
2023-11-16 18:01 ` David Edelsohn
2023-11-16 18:17 ` David Edelsohn
2023-11-16 18:52 ` Bruno Haible
2023-11-16 22:18 ` David Edelsohn
2023-11-16 22:46 ` Bruno Haible
2023-11-16 23:10 ` Arsen Arsenović
2023-11-17 8:33 ` Richard Biener
2023-11-17 8:49 ` Arsen Arsenović
2023-11-17 12:24 ` Bruno Haible
2023-11-17 13:06 ` Arsen Arsenović
2023-11-16 23:38 ` David Edelsohn
2023-11-17 0:07 ` Bruno Haible [this message]
2023-11-17 0:15 ` David Edelsohn
[not found] ` <84B39BF1-33D5-488E-8CF5-D08B09417568@gmail.com>
2023-11-16 17:44 ` David Edelsohn
2023-11-16 18:47 ` Bruno Haible
2023-11-16 18:50 ` Arsen Arsenović
2023-11-16 18:59 ` Bruno Haible
2023-11-16 19:14 ` Arsen Arsenović
2023-11-19 19:49 ` Bruno Haible
2023-11-15 14:14 ` [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-11-15 15:51 ` Xi Ruoyao
2023-11-16 18:48 ` Arsen Arsenović
2023-11-15 17:19 ` David Edelsohn
2023-11-16 18:33 ` Arsen Arsenović
2023-11-16 21:11 ` Arsen Arsenović
2023-11-16 21:40 ` David Edelsohn
2023-11-16 22:19 ` Arsen Arsenović
2023-11-16 22:30 ` David Edelsohn
2023-11-16 22:32 ` Arsen Arsenović
2023-11-16 23:59 ` David Edelsohn
2023-11-17 8:34 ` Arsen Arsenović
2023-11-17 8:50 ` Richard Biener
2023-11-17 8:56 ` Arsen Arsenović
2023-11-17 14:41 ` David Edelsohn
2023-11-17 15:16 ` Arsen Arsenović
2023-11-17 16:07 ` David Edelsohn
2023-11-18 18:10 ` Arsen Arsenović
2023-11-19 21:55 ` Bruno Haible
2023-11-19 23:00 ` Bruno Haible
2023-11-19 23:06 ` Andrew Pinski
2023-11-20 1:17 ` David Edelsohn
2023-11-20 21:18 ` Arsen Arsenović
2023-11-20 21:38 ` David Edelsohn
2023-11-21 0:44 ` Arsen Arsenović
2023-11-20 23:00 ` Bruno Haible
2023-11-21 0:45 ` Arsen Arsenović
2023-11-21 13:13 ` Arsen Arsenović
2023-11-21 16:28 ` David Edelsohn
2023-11-21 20:58 ` Eric Gallager
2023-11-15 19:58 ` David Edelsohn
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=5798081.UuxTggG6dJ@nimes \
--to=bruno@clisp.org \
--cc=arsen@aarsen.me \
--cc=bug-gettext@gnu.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.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).