This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: .class code optimization

From: Mark Wielaard <mark at klomp dot org>
To: Adam Megacz <gcj at lists dot megacz dot com>
Cc: tromey at redhat dot com, Jeff Sturm <jsturm at one-point dot com>, Andrew Haley <aph at redhat dot com>, Lapo Luchini <lapo at lapo dot it>, java at gcc dot gnu dot org
Date: 12 Oct 2002 12:08:19 +0200
Subject: Re: .class code optimization
References: <Pine.LNX.4.44.0210111459420.8371-100000@ops2.one-point.com><864rbsbii1.fsf@nowhere.com> <87vg48a3tx.fsf@fleche.redhat.com> <86ptuga3cu.fsf@nowhere.com>

Hi,

On Sat, 2002-10-12 at 02:49, Adam Megacz wrote:
> 
> Yes.  I guess inlining within a 'compilation unit' would be ideal.
> Thus, if you pass your entire source tree to gcj in one invocation,
> you'll get inter-class inlining.

We could at least take a package as a compilation unit.
A ClassLoader can set a Package to sealed which means that no classes
can be loaded in that package from a different origin.
See java.lang.ClassLoader.definePackage().

Cheers,

Mark

References:
- Re: .class code optimization
  - From: Jeff Sturm
- Re: .class code optimization
  - From: Adam Megacz
- Re: .class code optimization
  - From: Tom Tromey
- Re: .class code optimization
  - From: Adam Megacz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]