[concurrency-interest] synchronized block expansion

studdugie studdugie at gmail.com
Wed Feb 8 17:51:16 EST 2006

I'm not sure I will be breaking a concurrency-interest nettiquette by
posting my question here but I could think of a better place to ask
it, so if I am, scold me gently :)

Here is the code fragment in question:

long wait;
synchronized( timeouts )
    if( timeouts.isEmpty() )
        wait = 0;
        timeouts.remove( wait = timeouts.firstLong() );

if( 0 == wait )
    semaphore.await( wait, EnclosingClass.this.units );

timeouts = long primitive java.util.SortedSet
semaphore = java.util.concurrent.CountDownLatch w/ a count of 1
EnclosingClass.this.units = java.util.concurrent.TimeUnit

I know that code w/i a synchronized block code is not allowed to be
reordered but that doesn't mean that the scope of the synchronized
block can't be expanded.  So my question is, what is the probablity
that Sun's hotspot compiler would expand the synchronized block to
include the semaphore.await() ? Or am I just being paranoid?


More information about the Concurrency-interest mailing list