------- Additional Comments From bonzini at gcc dot gnu dot org  2005-08-23 
14:51 -------
> It looks like the problem is that we don't remove the synchronization
> for nextDouble() even though the test case is single-threaded.

If we can remove even only half of the synchronization overhead, by
synchronizing just once per nextDouble() call, it's a win.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23283

Reply via email to