This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: BC ABI stuff
- From: Andrew Haley <aph at redhat dot com>
- To: Ranjit Mathew <rmathew at gmail dot com>
- Cc: tromey at redhat dot com, GCJ <java at gcc dot gnu dot org>
- Date: Mon, 16 Aug 2004 10:10:49 +0100
- Subject: Re: BC ABI stuff
- References: <87brhen56e.fsf@fleche.redhat.com><41206A96.8050700@gmail.com>
Ranjit Mathew writes:
> May I request that a section on the BC-ABI implementation
> be added to either the GCJ manual or the GCC Internals
> manual? You can perhaps copy-paste much of the material
> from your paper in the GCC summit.
Yes. We need to do this.
> Actually, it would be nice to have such a section for
> GCJ's implementation as a whole - class and object
> representation, interaction with the GC, etc.
Indeed it would.
> Tom Tromey wrote:
> > flag to indicate "don't try to read dependent classes, and don't
> > bother warning me about it either", but those things are being worked
>
> Sorry, I'm a bit rusty on this stuff, but why exactly? If
> I refer to a class directly (i.e. not via, say, Class.forName())
> isn't the compiler supposed to check that class?
If the class resolution isn't done until runtime, there's no point in
checking anything at compile time. Besides, it might not be possible:
the class might not be in the classpath.
Andrew.