From: Thomas Neumann <thomas.neumann@in.tum.de>
To: gcc-patches@gcc.gnu.org
Subject: PING^2: [PATCH v3] eliminate mutex in fast path of __register_frame
Date: Fri, 26 Aug 2022 15:01:59 +0200 [thread overview]
Message-ID: <90477551-1638-1669-d54e-685257020479@in.tum.de> (raw)
Summary: __register_frame and the corresponding _Unwind_Find_FDE use a
global mutex for frame registration and unwinding. This can lead to very
poor performance on machines with high core counts. This patch organizes
the frames in a b-tree with read-optimized synchronization instead,
which allows for fully parallel unwinding.
See:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597256.html
Best
Thomas
reply other threads:[~2022-08-26 13:02 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=90477551-1638-1669-d54e-685257020479@in.tum.de \
--to=thomas.neumann@in.tum.de \
--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).