As I start to look at the multithreading aspects of the Smalltalk implementation I can see a situation where two threads could be running down the GWT lookup path both looking for the same implementation. I was thinking of making the lookup synchronized but then what if two threads are in the GWT pipeline looking for the same implementation. One gets to the lookup first and finds the method. Now is it possible that the second thread had entered the call site but is suspended between the site and the lookup? In that case the lookup will have been done but the second thread has passed the GWT for it (its added to the start).
I am thinking that I may just accept the fact that there could be duplicate GWTs in the chain. Or is there a better approach? Thanks mark
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev