From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: David Taylor <dtaylor@emc.com>, gdb@sources.redhat.com
Subject: Re: macros, debug information, and parse_macro_definition
Date: Sun, 04 May 2003 19:41:00 -0000 [thread overview]
Message-ID: <3EB56C9A.6070207@redhat.com> (raw)
In-Reply-To: <vt2d6j1f8vw.fsf@zenia.red-bean.com>
> Actually, I think that David's proposed representation will compress
> really well, with no new linker work. The linker's current behavior
> will do everything that's needed.
>
> Each entry in the .stab section is a fixed-size record; the textual
> portion of the stab is represented as an offset into the .stabstr
> section, which contains null-terminated strings. The .stabstr section
> is a SHT_STRTAB type section, which means that the linker will
> automatically factor out duplicates. So if two .stab entries have the
> same text, they'll end up pointing to the same bytes in .stabstr in
> the final executable.
>
> In David's proposed representation, #including a file into many
> different .o files will produce stabs entries with identical strings,
> so they'll all get factored out nicely.
>
> All this is completely independent of the BINCL/EINCL -> EXCL
> compression the linker also does for STABS, to factor out duplicated
> entries from the .stab section itself.
So the stabs mechanism might compress down to something useable. Ah,
the irony :-)
Andrew
prev parent reply other threads:[~2003-05-04 19:41 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
2003-04-29 16:51 ` David Taylor
2003-05-02 19:21 ` Jim Blandy
2003-05-04 19:41 ` Andrew Cagney [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=3EB56C9A.6070207@redhat.com \
--to=ac131313@redhat.com \
--cc=dtaylor@emc.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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).