This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
generating shared libs
- To: "'java-discuss at sources dot redhat dot com'" <java-discuss at sources dot redhat dot com>
- Subject: generating shared libs
- From: "Immanuel, Gidado-Yisa" <avm3 at cdc dot gov>
- Date: Fri, 22 Dec 2000 12:50:30 -0500
I'm sure these questions have been addressed
before, but I couldn't find it in the archives.
I am able to create object files for a single
class, but
1. How do I combine several object files
(created from .javaJ) to make my own shared
lib (.so)?
2. Also, is there a convenient way to do [1]
but starting from a jar file?
Thanks,
Gidado
-----Original Message-----
From: Anthony Green [mailto:green@redhat.com]
Sent: Thursday, December 21, 2000 8:46 PM
To: 'Boehm, Hans'
Cc: 'java-discuss@sources.redhat.com'; 'tromey@redhat.com'
Subject: RE: Jv_AllocBytesChecked (Was: What is wrong with Vector?)
On Thursday, December 21, 2000 4:33 PM, Boehm, Hans [SMTP:hans_boehm@hp.com]
wrote:
> The gcc man page claims this has only a size impact. (I assume
> it does effectively add flow edges to the analysis, but I'm not sure that
> has much impact if you only pass through the exception.)
I think it works like this...
Architectures using sjlj exceptions take a code size and performance hit.
Architectures using pc range tables for exceptions take a data size hit.
AG