From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Vincenzo Innocente <Vincenzo.Innocente@cern.ch>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: reducing the contention in dl_iterate_phdr (reloaded)
Date: Wed, 22 Nov 2023 11:05:31 -0300 [thread overview]
Message-ID: <273564f9-9348-44c0-b8ce-90a459beadff@linaro.org> (raw)
In-Reply-To: <CEE8AFFD-5F56-4C9F-8E28-5E56212E6A00@cern.ch>
On 22/11/23 08:13, Vincenzo Innocente via Libc-help wrote:
> I found this old thread about lack of concurrency in dl_iterate_phdr that affects gcc unwinding.
> https://sourceware.org/pipermail/libc-help/2020-May/005275.html
>
> I discover this issue while experimenting with C++23 std::stacktrace in a multithread application.
>
> Has been made any progress on the subject since May 2020?
Starting with version 2.35, glibc provides _dl_find_object [1] which is
used by libgcc unwinder [2] functions to fix the scalability issues.
The libstdc++ must be built against a glibc 2.35 headers to enable it.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586170.html
[2] https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg273082.html
prev parent reply other threads:[~2023-11-22 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 11:13 Vincenzo Innocente
2023-11-22 14:05 ` Adhemerval Zanella Netto [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=273564f9-9348-44c0-b8ce-90a459beadff@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Vincenzo.Innocente@cern.ch \
--cc=libc-help@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).