This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Jessie security providers can't be precompiled
- From: Bryce McKinlay <mckinlay at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: java-patches at gcc dot gnu dot org
- Date: Wed, 30 Nov 2005 19:55:39 -0500
- Subject: Re: Jessie security providers can't be precompiled
- References: <17293.36251.322183.524897@zapata.pink>
Andrew Haley wrote:
or rather, if they are precompiled we still load the bytecode anyway.
This is because VMCompiler depends on the security providers, so any
that are loaded before VMCompiler is initialized are interpreted. The
cure is to bypass the security provider machinery.
Would it make sense to include a small C implementation of MD5 to be
used by VMCompiler? Initializing the providers was bringing a LOT of
code into the application startup/runtime bootstrap code path. I suppose
this fixes it too, since we're only calling MD5 directly, but a native
implementation may still be smaller/faster?
Bryce