From: Jason Merrill <jason@redhat.com>
To: "Moore, Catherine" <Catherine_Moore@mentor.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Matthew Fortune <Matthew.Fortune@imgtec.com>,
Richard Henderson <rth@redhat.com>,
Ian Lance Taylor <iant@google.com>
Subject: Re: [RFA] Compact EH Patch
Date: Wed, 09 Sep 2015 20:45:00 -0000 [thread overview]
Message-ID: <55F09802.1050607@redhat.com> (raw)
In-Reply-To: <FD3DCEAC5B03E9408544A1E416F112420192C8DEFB@NA-MBX-04.mgc.mentorg.com>
On 07/30/2015 04:14 PM, Moore, Catherine wrote:
> This patch implements a more compact format for exception handling data. Although I don't have recent numbers for the amount of compression achieved, an earlier measurement showed a 30% reduction in the size of EH data for libstdc++.
>
> A design document detailing the new format is available (https://github.com/MentorEmbedded/cxx-abi/blob/master/MIPSCompactEH.pdf).
>
> This implementation enables the new format for MIPS targets only, but the generic pieces to enable the new format for other architectures is in place.
Hi, sorry for the slow response.
I'm surprised that there was no mention of this design on the ABI list,
especially since you've decided to post the design document to its git
repository.
I'm skeptical about the explicit rejection of asynchronous backtracing;
this is an important capability for debug traces on hosted systems,
which is why the compiler flag is on by default in many linux
distributions. The document mentions using libunwind instead, but that
wouldn't help, as libunwind relies on the same unwind information. So
it seems to me that the objective in 1.2 of supporting both unhosted and
Linux-hosted programs isn't sufficiently met.
Jason
next prev parent reply other threads:[~2015-09-09 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:07 Moore, Catherine
2015-08-14 19:58 ` Moore, Catherine
2015-09-09 20:45 ` Jason Merrill [this message]
2015-09-09 23:53 ` Richard Henderson
2015-09-14 19:32 ` Moore, Catherine
2015-09-18 19:34 ` Richard Henderson
2015-10-05 23:14 ` Moore, Catherine
2015-10-06 16:12 ` Richard Henderson
2015-11-25 17:13 ` Moore, Catherine
2015-12-01 21:32 ` Moore, Catherine
2015-12-01 21:33 ` Jason Merrill
2015-12-02 13:39 ` Jonathan Wakely
2015-12-13 22:12 ` Moore, Catherine
2015-10-28 16:44 ` Matthew Fortune
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=55F09802.1050607@redhat.com \
--to=jason@redhat.com \
--cc=Catherine_Moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=rth@redhat.com \
/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).