From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/dwarf] Support for attributes pointing to a different CU
Date: Tue, 28 Sep 2004 22:43:00 -0000 [thread overview]
Message-ID: <vt2oejqm2zq.fsf@zenia.home> (raw)
In-Reply-To: <20040924003412.GB10500@nevyn.them.org>
I take it the reason we can't just fill in all the per_cu->psymtab
values when we build the psymtabs in the first place is that we don't
actually build the CU index until we see a CU that contains (or might
contain) inter-CU references. So we'd have to go back and record the
psymtabs we'd already created anyway. Is that right?
We're constructing a psymtab for every CU we see; does it save much
time or space to avoid creating a twenty-byte structure as well? I
understand that this is time- and space-critical code, but if the hair
isn't a noticable win, I'd rather it not go in.
next prev parent reply other threads:[~2004-09-28 22:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:57 Daniel Jacobowitz
2004-09-23 22:19 ` Jim Blandy
2004-09-23 22:33 ` Daniel Jacobowitz
2004-09-24 0:34 ` Daniel Jacobowitz
2004-09-28 22:43 ` Jim Blandy [this message]
2004-09-28 22:51 ` Jim Blandy
2004-09-28 22:57 ` Jim Blandy
2004-10-04 0:41 ` Daniel Jacobowitz
2004-10-04 22:12 ` Jim Blandy
2004-10-04 23:35 ` Daniel Jacobowitz
2004-10-05 5:13 ` Jim Blandy
2004-09-28 23:07 ` Jim Blandy
2004-10-03 16:28 ` Daniel Jacobowitz
2004-09-29 17:52 ` Jim Blandy
2004-10-03 16:12 ` Daniel Jacobowitz
2004-10-04 21:17 ` Jim Blandy
2004-10-04 21:22 ` Daniel Jacobowitz
2004-10-05 5:07 ` Jim Blandy
2004-10-05 13:48 ` Daniel Jacobowitz
2004-10-05 16:13 ` Jim Blandy
2004-10-05 16:11 ` Jim Blandy
2004-10-05 18:01 ` Daniel Jacobowitz
2004-10-05 19:24 ` Jim Blandy
2004-09-29 17:54 ` Jim Blandy
2004-09-29 19:53 ` Jim Blandy
2004-10-03 16:16 ` Daniel Jacobowitz
2004-09-29 20:19 ` Jim Blandy
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=vt2oejqm2zq.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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