b53f78eef1
Now caching of the last access slot covers GetterSlot instances as well and getter is always called for such slots 2. Fixing a potential race condition in setBySetter when a setter slot becomes an ordinary slot in response to a setter returning a value. During execution of setBySetter a different thread can see initial null value in slot.value instead of the result of setter call as it is possible that JVM will first update slot.flags and only then slot.value for that thread. The fix replaces the old getter slot by an ordinary one under synchronized block for that I added new getSlotPosition method and updated the rest of code accordingly. git-svn-id: svn://10.0.0.236/trunk@134679 18797224-902f-48f8-a5cc-f745e15eee43