From: Daniel Berlin <dberlin@dberlin.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: A hack for DW_FORM_ref_addr
Date: Thu, 31 Jul 2003 22:33:00 -0000 [thread overview]
Message-ID: <FE9A2BFA-C3A6-11D7-A56D-000A95A34564@dberlin.org> (raw)
In-Reply-To: <20030731182857.GB14520@lucon.org>
>
> Since DW_FORM_ref_addr requires it, I don't see there is an easy way
> out. I guess I could only save those used by DW_FORM_ref_addr.
>
Back when this support was implemented the first (or was it the second)
time, I just had it keep around the last 5 or 10 referenced compilation
units full of dies in an LRU cache, and just reread non-cached CU's as
necessary.
I think Daniel planned on doing something similar for the third rewrite.
>
> H.J.
next prev parent reply other threads:[~2003-07-31 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 21:42 DW_FORM_ref_addr dosn't work H. J. Lu
2003-07-30 21:45 ` Daniel Jacobowitz
2003-07-30 21:52 ` H. J. Lu
2003-07-30 21:55 ` Daniel Jacobowitz
2003-07-30 22:01 ` H. J. Lu
2003-07-31 5:16 ` H. J. Lu
2003-07-31 16:16 ` A hack for DW_FORM_ref_addr H. J. Lu
2003-07-31 18:22 ` Daniel Jacobowitz
2003-07-31 18:29 ` H. J. Lu
2003-07-31 22:33 ` Daniel Berlin [this message]
2003-07-31 21:21 ` H. J. Lu
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=FE9A2BFA-C3A6-11D7-A56D-000A95A34564@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.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