[concurrency-interest] a volatile bug?

David Holmes davidcholmes at aapt.net.au
Sat May 19 19:12:10 EDT 2012

It is also very difficult to run tests in a way that tests all possible generated code from the JITs. The OSR form can be different from the "normal" form which can be different from a forced compilation via -Xcomp.

But we definitely need better coverage here.


> -----Original Message-----
> From: concurrency-interest-bounces at cs.oswego.edu
> [mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of Doug Lea
> Sent: Saturday, 19 May 2012 11:25 PM
> To: viktor ?lang
> Cc: concurrency-interest at cs.oswego.edu
> Subject: Re: [concurrency-interest] a volatile bug?
> On 05/19/12 09:16, √iktor Ҡlang wrote:
> > Wait, what, there's no JMM tests?
> There is not, to my knowledge, a "hotspot JMM Test suite"
> (which is out of my scope).  But there are (three forms of)
> j.u.c test suites, that together test most JMM requirements.
> But there ought to be a separate one to mop up coverage holes.
> -Doug
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

More information about the Concurrency-interest mailing list