public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Keith Walker <keith.walker@arm.com>
Cc: gdb@sources.redhat.com
Subject: Re: macros, debug information, and parse_macro_definition
Date: Tue, 29 Apr 2003 17:13:00 -0000	[thread overview]
Message-ID: <DF7F281D-7A65-11D7-B237-000A95A34564@dberlin.org> (raw)
In-Reply-To: <4.3.2.7.2.20030429170707.02ac6180@mhsun1.maidenhead.arm.com>


On Tuesday, April 29, 2003, at 12:16  PM, Keith Walker wrote:

> At 11:55 29/04/2003 -0400, Daniel Berlin wrote:
>> It's trivial to do macro information compression, unlike normal 
>> dwarf2 info compression, because the macro info has no references. It 
>> is what it is.  With a smart algorithm (it's a bit tricky to keep the 
>> semantics the same after merging all the macro infos), you could 
>> simply take all the macro infos, merge them, make one macro info, and 
>> point all the debug sections at it.
>> I think, anyway.
>
> I'm not sure whether your comment is about macro info in general or 
> about macro info in DWARF2.
>
> Unfortunately, for DWARF2 debugging information, I don't think it is 
> quite so easy in that the macro information can include file start/end 
> entries which refer to file entries in the associated line number 
> information -
I'm aware, i wrote GCC's DWARF2 macro info support.
:)

> so you would also have to do something about merging the line number 
> tables as well;
This is also trivial, since it's just going to require updating an 
attribute on all the DIEs, not moving/removing DIE's (which is the only 
real thing that generates problems in merging DWARF2 info).

>  and hence update all other entries that refer to the file entries.
Still trivial compared to what you have to do for DWARF2 info in 
general.

>
> Keith
>

  reply	other threads:[~2003-04-29 17:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 16:40 David Taylor
2003-04-22 20:06 ` Kevin Buettner
2003-04-24  3:08 ` Jim Blandy
2003-04-24 15:12   ` David Taylor
2003-04-29 14:55     ` Andrew Cagney
2003-04-29 15:55       ` Daniel Berlin
2003-04-29 16:24         ` Keith Walker
2003-04-29 17:13           ` Daniel Berlin [this message]
2003-04-29 16:51       ` David Taylor
2003-05-02 19:21       ` Jim Blandy
2003-05-04 19:41         ` Andrew Cagney

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=DF7F281D-7A65-11D7-B237-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gdb@sources.redhat.com \
    --cc=keith.walker@arm.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).