From: David Edelsohn <dje.gcc@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Thomas Neumann via Gcc <gcc@gcc.gnu.org>,
Thomas Neumann <tneumann@users.sourceforge.net>
Subject: Re: performance of exception handling
Date: Mon, 11 May 2020 10:36:32 -0400 [thread overview]
Message-ID: <CAGWvnynP2gji-XBVY9=LHWR_5wTp6eXGQsxCRSLU9pzCJM8LZA@mail.gmail.com> (raw)
In-Reply-To: <874ksmg3fb.fsf@oldenburg2.str.redhat.com>
On Mon, May 11, 2020 at 6:47 AM Florian Weimer via Gcc <gcc@gcc.gnu.org> wrote:
> My current preferred solution is something that moves the entire code
> that locates the relevant FDE table into glibc. This is all the code in
> _Unwind_IteratePhdrCallback until the first read_encoded_value_with_base
> call. And the callback mechanism would be gone, so _Unwind_Find_FDE
> would call __dl_ehframe_find (see below) and then the reamining
> processing in _Unwind_IteratePhdrCallback.
Not all GCC/G++ targets are GNU/Linux and use GLIBC. A duplicate
implementation in GLIBC creates its own set of advantages and
disadvantages.
Thanks, David
next prev parent reply other threads:[~2020-05-11 14:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 8:14 Thomas Neumann
2020-05-11 10:40 ` Florian Weimer
2020-05-11 13:59 ` Thomas Neumann
2020-05-11 14:22 ` Florian Weimer
2020-05-11 15:14 ` size of exception handling (Was: performance of exception handling) Moritz Strübe
2020-05-12 7:20 ` Freddie Chopin
2020-05-12 7:47 ` Oleg Endo
2020-05-13 9:13 ` Jonathan Wakely
2020-05-12 9:16 ` size of exception handling Florian Weimer
2020-05-12 9:44 ` Freddie Chopin
2020-05-12 11:11 ` Jonathan Wakely
2020-05-12 11:17 ` Moritz Strübe
2020-05-12 11:29 ` Florian Weimer
2020-05-12 12:01 ` Moritz Strübe
2020-05-12 11:07 ` size of exception handling (Was: performance of exception handling) Jonathan Wakely
2020-05-12 20:56 ` Freddie Chopin
2020-05-12 22:39 ` Jonathan Wakely
2020-05-12 22:48 ` Jonathan Wakely
2020-05-13 8:04 ` David Brown
2020-05-12 9:03 ` size of exception handling Florian Weimer
2020-05-11 14:36 ` David Edelsohn [this message]
2020-05-11 14:52 ` performance " Florian Weimer
2020-05-11 15:12 ` David Edelsohn
2020-05-11 15:24 ` Florian Weimer
2020-05-12 6:08 ` Thomas Neumann
2020-05-12 7:15 ` Richard Biener
2020-05-12 7:30 ` Thomas Neumann
2020-05-12 9:01 ` Richard Sandiford
2020-05-13 1:13 ` Thomas Neumann
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='CAGWvnynP2gji-XBVY9=LHWR_5wTp6eXGQsxCRSLU9pzCJM8LZA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=tneumann@users.sourceforge.net \
/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).