Changeset: 4a0cedf169a2
Author:jrose
Date: 2012-07-21 14:10 -0700
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/4a0cedf169a2
meth-lazy: remove about 1kLOC more
+ meth-lazy-7023639.rmcode.patch
! series
___
mlvm-dev mailing list
Changeset: 905bcd21d2bb
Author:jrose
Date: 2012-07-21 16:50 -0700
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/905bcd21d2bb
meth-lazy: incorporate review comments
! meth-lazy-7023639.rmcode.patch
___
mlvm-dev mailing list
Changeset: 3b3f4347ab7e
Author:jrose
Date: 2012-07-21 16:55 -0700
URL: http://hg.openjdk.java.net/mlvm/mlvm/jdk/rev/3b3f4347ab7e
meth-lazy: consolidate changes made during review
- meth-lazy-7023639.bmh.patch
- meth-lazy-7023639.init.patch
+ meth-lazy-7023639.review.patch
-
On Jul 13, 2012, at 2:41 AM, John Rose wrote:
Here is that webrev:
http://cr.openjdk.java.net/~jrose/7023639/webrev.jdk.00/
These are the changes to JDK code that accompany the JVM changes already
under review.
I have updated both webrevs to their final contents, as follows:
On Jul 18, 2012, at 1:43 AM, Aleksey Shipilev wrote:
This feels outright wrong:
+static MapString, Data CACHE = new IdentityHashMap();
I couple of questions pops out in my mind:
1. Is this code supposed to be thread-safe? It is then wrong to use
unguarded IdentityHashMap without
