Mladen Turk responded to the concerns by Weldon Washburn about the
"light-weight native calls" in the thread "VM/Classlibrary Interface
(take 2)". He explained in more detail how he thinks those light-weight
calls could work, they should avoid the overhead for native calls.
Mladen and Tim Ellison
Santiago Gala wrote:
IIRC, the (JVM spec v2) requirement for .equals String literals to be
(==)identical only holds for Strings in the same .class file, but I
could be wrong.
I believe the requirement is stronger than that. Any two
String literals (i.e., String constants from class files)
that
I was wondering what similarities on-stack replacement of JITed code
have with suspension with code patching.
On 9/9/05, Xiao-Feng Li <[EMAIL PROTECTED]> wrote:
> Thanks, Rodrigo and Shudo. ORP had a similar approach as code patching
> previously, which we called "IP hijacking". We found, as you
El jue, 08-09-2005 a las 15:51 +0100, Peter Edworthy escribió:
(...snip...)
> [long version]
> Cleaning up Strings that are only used in a particular classloader has
> a
> slight catch; because of the 'Strings containing the same characters
> are
> the same object' clause. This requires keeping a l
