This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: patches to re-direct _Jv_RegisterClass
- To: Per Bothner <per at bothner dot com>
- Subject: Re: patches to re-direct _Jv_RegisterClass
- From: Tom Tromey <tromey at redhat dot com>
- Date: 06 Jul 2001 13:31:34 -0600
- Cc: java-patches at gcc dot gnu dot org
- References: <m2u218owwn.fsf@kelso.bothner.com> <871yocarlq.fsf@creche.redhat.com> <m2n16y4g3v.fsf@kelso.bothner.com> <87lmmh3g6a.fsf@creche.redhat.com> <m2ofrdbqu0.fsf@kelso.bothner.com>
- Reply-To: tromey at redhat dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Per> You basically have two sensible choices for each .so:
Per> (1) Symbols have global visibility; classes are managed by the
Per> system ClassLoader; library either specified at link time with -l
Per> or at runtime at dlopen *with* RTLD_GLOBAL set.
Per> (2) Symbols are only visible with a shared library; classes are
Per> managed by a SharedLibLoader and are only visible by going
Per> through that ClassLoader; library linked at runtime at dlopen
Per> *without* RTLD_GLOBAL set.
So if I understand correctly this means that it makes sense for us to
have both .so loading built in to the system class loader as well as a
SharedLibLoader. In that case I think we'd definitely want your
SharedLibLoader code.
Tom