Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Support for comdat-based dwarf debug info reduction for types.
Date: Sat, 17 Jan 2009 03:33:00 -0000	[thread overview]
Message-ID: <20090117033152.GM24105@adacore.com> (raw)
In-Reply-To: <20081106210721.392FF1C799C@localhost>

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?

Speaking of GCC, do you know the status of the enhancement?

> 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 :).

-- 
Joel


  reply	other threads:[~2009-01-17  3:33 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 [this message]
2009-01-17 18:56   ` Doug Evans

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=20090117033152.GM24105@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dje@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