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: binary compatibility ABI (was: Re: [boehm-gc] Import 6.3 alpha1)

From: Andrew Haley <aph at redhat dot com>
To: Jeff Sturm <jsturm at one-point dot com>
Cc: Bryce McKinlay <bryce at mckinlay dot net dot nz>, Ranjit Mathew <rmathew at hotmail dot com>, <java at gcc dot gnu dot org>
Date: Wed, 20 Aug 2003 18:16:15 +0100
Subject: Re: binary compatibility ABI (was: Re: [boehm-gc] Import 6.3 alpha1)
References: <839A9B20-CEA8-11D7-AD15-003065F97F7C@mckinlay.net.nz><Pine.LNX.4.44.0308181435250.5528-100000@ops2.one-point.com>

Jeff Sturm writes:
 > 
 > My impression is that libgcj is vital to overall application performance.
 > I doubt users can replace code in java.lang.* without breaking things.
 > Perhaps libgcj should distinguish bootclasspath code from the rest, and
 > not allow runtime class replacment in the former?

IMO libgcj should be linked so that every internal reference is
direct, so nothing in that library may be replaced at runtime -- as
you say, this would be very fragile and insecure.

It would be good to make this change at the same time as the binary
compatibility ABI changes.

Andrew.

Follow-Ups:
- Re: binary compatibility ABI (was: Re: [boehm-gc] Import 6.3 alpha 1)
  - From: Tom Tromey

References:
- Re: binary compatibility ABI (was: Re: [boehm-gc] Import 6.3 alpha 1)
  - From: Bryce McKinlay
- Re: binary compatibility ABI (was: Re: [boehm-gc] Import 6.3 alpha1)
  - From: Jeff Sturm

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