From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, archer@sourceware.org
Subject: Re: Initial psymtab replacement results
Date: Wed, 16 Dec 2009 19:52:00 -0000 [thread overview]
Message-ID: <20091216195206.769429E5@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of Wednesday, 16 December 2009 12:46:46 -0700 <m3k4wmk8gp.fsf@fleche.redhat.com>
> Nothing requires a compiler to emit .debug_aranges for a CU. It is an
> optional index, at least by my reading:
Right. I guess I didn't consider the issue of linking together things
built with different compilers.
> This issue affects .debug_pub* as well.
Right. For all such things this suggests some utility in having headers or
something to identify "I was emitted at/after link time" so that any
post-processor (or equivalent DWARF-savvy linker) would indicate when it
had wiped away such concerns.
Thanks,
Roland
next prev parent reply other threads:[~2009-12-16 19:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 21:54 Tom Tromey
2009-12-11 23:10 ` Tom Tromey
2009-12-11 23:59 ` Daniel Jacobowitz
2009-12-14 22:40 ` Tom Tromey
2009-12-14 23:09 ` Daniel Jacobowitz
2009-12-15 23:39 ` Tom Tromey
2009-12-16 3:01 ` Roland McGrath
2009-12-16 18:20 ` Tom Tromey
2009-12-16 18:57 ` Roland McGrath
2009-12-16 19:46 ` Tom Tromey
2009-12-16 19:52 ` Roland McGrath [this message]
2009-12-16 18:11 ` Daniel Jacobowitz
2009-12-16 19:31 ` Tom Tromey
2009-12-23 18:29 ` Tom Tromey
2009-12-23 18:35 ` Daniel Jacobowitz
2009-12-24 17:07 ` Tom Tromey
2010-01-06 23:05 ` Tom Tromey
2009-12-17 16:39 ` Paul Pluzhnikov
2009-12-17 16:53 ` Daniel Jacobowitz
2009-12-17 17:20 ` Paul Pluzhnikov
2009-12-17 18:16 ` Daniel Jacobowitz
2009-12-18 23:58 ` Tom Tromey
2009-12-21 13:54 ` Daniel Jacobowitz
2009-12-21 21:29 ` Tom Tromey
2009-12-15 1:04 ` Roland McGrath
2009-12-15 18:36 ` Tom Tromey
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=20091216195206.769429E5@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=archer@sourceware.org \
--cc=drow@false.org \
--cc=tromey@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).