From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Thu Jan 07 1999 - 04:43:59 EST
On Jan 7, 1999, Godmar Back <gback@cs.utah.edu> wrote:
> I think he means the speed with which a jit compiled function calls
> a JNI function. This does not depend on the signature being pre-parsed,
> it simply depends on the quality of the code emitted in Kaffe_JNI_Wrapper.
> Or am I missing something here?
I think Kaffe_JNI_Wrapper is fast enough already, the problem is the
other way round: JNI invocations (i.e., from native to Java) are slow,
because the signature must be parsed and the arguments must be
converted to whatever format the Java code expects according to this
signature.
> About the static/dynamic issue: what will be the lookup rule if a name
> is both hard-coded and can be found dynamically?
It depends on the order in which libraries were loaded. libltdl (the
libtool library that implements portable dlopening) will dlsym from a
single library at a time, so I have created a loop that tries a dlsym
for one library at a time, until it is found or no more libraries are
available.
However, if more than one library is statically linked, it is possible
that a symbol from the second library will be found in the dlsym of
the first one. libtool may modify this in the future, but this is
current state of libltdl.
> Also, are there going to be knobs to say which lib you want to link
> statically?
I haven't created any, but it should be as easy as adding `-static' to
the link command of that particular library.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:31 EDT