This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Option to automatically generate missing exceptions and methods
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: java at gcc dot gnu dot org
- Date: Wed, 12 Mar 2003 08:35:19 -0500 (EST)
- Subject: Re: Option to automatically generate missing exceptions and methods
On Tue, 11 Mar 2003, [iso-8859-1] Øyvind Harboe wrote:
> Part of the problem of getting GCJ to work can sometimes
> be that various classes and methods are not supported
> in Classpath.
-fno-assume-compiled may help, at least when compiling from
bytecode to native. For source compiles there isn't much gcj can do about
missing classes, as Tom explained.
Gcj requires that a .jar file be fully resolved at compile time. The JRE
doesn't. That's a known problem. The -fno-assume-compiled option
(partially implemented for 3.4) adds a level of indirection for the
missing classes, allowing the bytecode interpreter to resolve them at
runtime, or never at all.
Jeff