From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Cary Coutant <ccoutant@google.com>
Subject: Re: [RFC] Support for comdat-based dwarf debug info reduction for types.
Date: Sat, 17 Jan 2009 18:56:00 -0000 [thread overview]
Message-ID: <e394668d0901171056n5d610c87h7b2a6d2c8b5afae2@mail.gmail.com> (raw)
In-Reply-To: <20090117033152.GM24105@adacore.com>
On Fri, Jan 16, 2009 at 7:31 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Doug,
>
>> Hi. Here is my current patch to support comdat-based dwarf debug info
>> reduction for types.
>>
>> http://wiki.dwarfstd.org/index.php?title=COMDAT_Type_Sections
>
> I don't remember anyone answering your email. That's too bad, because
> I think that any attempt at reducing the size of debugging info is
> interesting.
>
>> I'm hoping someone can find some to give me a review.
>> The patch can't go in today as the corresponding GCC support isn't
>> in the main trunk yet.
>
> Regarding timing, I don't think we have to wait for GCC. As far as I can
> tell, this would add a functionality without disturbing the current
> behavior, right? Or perhaps the problem is actual testing of your code?
Correct, it adds functionality without disturbing current behaviour.
[if there is a disturbance, that's a bug]
The patch has been well tested with and without the corresponding gcc
patch of Cary's. No claim is made that it couldn't use more testing
of course. :-) IIRC, there is one known bug, tracking of the source
file a type came from; I plan to fix that before the gdb release with
the patch goes out of course.
Depending on the relative timings of gdb/gcc tree status and releases,
we may want to get the gdb support in sooner rather than later (so gdb
releases support the feature when it is in gcc).
One reason for waiting might be that some other compiler might
implement the current proposal, and then the dwarf spec changes and
gdb has to support the old version. The proposal only has a few
remaining minor issues, and I think the probability of anything like
this happening is remote; I offer it for completeness' sake.
> Speaking of GCC, do you know the status of the enhancement?
We're waiting on gcc to enter stage1. The patch is ready, modulo AIUI
it hasn't been reviewed yet, and modulo I don't know how much gcc has
changed since the patch was last tested.
>> This patch is incomplete in that the proposal has moved the ODR signature
>> from the CU header to an attribute.
>> This is a trivial change, relative to the entire patch.
>
> Do you have an updated version of your patch. I've mostyl been hacking
> the dwarf2 reader, so hopefully someone more veteran can review the
> code eventually, but my comments will (hopefully!) be better than
> nothing :).
I will resubmit a patch against current CVS head next week.
The patch is currently in the archer-dje-dwarf-sig8 archer branch.
Thanks.
prev parent reply other threads:[~2009-01-17 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 21:08 Doug Evans
2009-01-17 3:33 ` Joel Brobecker
2009-01-17 18:56 ` Doug Evans [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=e394668d0901171056n5d610c87h7b2a6d2c8b5afae2@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=ccoutant@google.com \
--cc=gdb-patches@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