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: Are non-SJLJ exceptions busted on linux/x86?

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Scott Gilbertson <scottg at mantatest dot com>, Mohan Embar <gnustuff at thisiscool dot com>, java at gcc dot gnu dot org
Date: Thu, 17 Nov 2005 17:12:29 -0500
Subject: Re: Are non-SJLJ exceptions busted on linux/x86?
References: <200511172157.jAHLvsWX020983@earth.phy.uc.edu>

Andrew Pinski wrote:

F) Because someday gcj might work for no-filesystem environments, but only if it can make a static binary

That is a hard thing to do as java is a class/file based system.

Not necessarily. The J2ME CLDC, for example, has no "File" class.

One more thing, Objective-C really has the same issues as gcj and static
linking as both are very dynamic languages and can load classes at runtime
via a string which is why static linking will never work correctly with
java and Objective-C.

It is definitely problematic to mix the dynamic aspects of Java with static compilation. However, this does not mean that static linking isn't useful. It is often quite possible, and desirable, to create an application that is safe to use with static linking for deployment in closed/controlled/embedded environments.

Bryce

References:
- Re: Are non-SJLJ exceptions busted on linux/x86?
  - From: Andrew Pinski

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