From: Ian Lance Taylor <ian@wasabisystems.com>
To: tromey@redhat.com
Cc: Daniel Jacobowitz <drow@false.org>, Andrew Haley <aph@redhat.com>,
java@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Binary Compatibility: debug info for compiled Java programs
Date: Thu, 10 Jun 2004 16:47:00 -0000 [thread overview]
Message-ID: <m3aczb1hsu.fsf@gossamer.airs.com> (raw)
In-Reply-To: <874qpjbcju.fsf@fleche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> The symbols in the otable (and actually I've been using shorthand
> here, we have a second "atable" for addresses as well -- same
> difference though) are resolved when the class ("Foo") is linked. In
> Java this is done at runtime, the JVM Spec (and perhaps the JLS) has
> information on the precise steps involved in class preparation and
> initialization.
By the way, Tom and Andrew, I meant to ask, but I forgot: would it
make sense to build the numeric otables and atables for the common
case, and then recompute only when required? I have to think that the
common case is pretty darn common--I'm sure people don't spend all
their time loading classes into different hierarchies. Perhaps you
already do this.
Ian
next prev parent reply other threads:[~2004-06-10 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:15 Andrew Haley
2004-06-09 13:09 ` Daniel Jacobowitz
2004-06-09 13:19 ` Andrew Haley
2004-06-09 13:29 ` Daniel Jacobowitz
2004-06-09 13:39 ` Andrew Haley
2004-06-09 22:17 ` Daniel Jacobowitz
2004-06-09 22:37 ` Tom Tromey
2004-06-10 16:37 ` Daniel Jacobowitz
2004-06-10 16:42 ` Tom Tromey
2004-06-10 16:47 ` Ian Lance Taylor [this message]
2004-06-10 16:58 ` Andrew Haley
2004-06-10 17:12 ` Ian Lance Taylor
2004-06-10 17:25 ` Andrew Haley
2004-06-10 16:44 ` Andrew Haley
2004-06-10 16:54 ` Daniel Jacobowitz
2004-06-09 14:13 ` Per Bothner
2004-06-09 14:20 ` Andrew Haley
2004-06-09 20:46 ` Anthony Green
2004-06-09 21:26 ` Andrew Cagney
2004-06-09 22:11 ` Anthony Green
2004-06-11 13:04 ` Andrew Haley
2004-06-11 15:11 ` Andrew Cagney
2004-06-11 15:17 ` Andrew Haley
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=m3aczb1hsu.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=aph@redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=java@gcc.gnu.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