Just to add my 2 euro-cents (basically Bart said it all already, tho)
My impressions are that:
1. Double checked locking is fundamentally broken:
http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html
2. Even if you verify by hand the resulting machine code, you still need
On Sun, Aug 28, 2011 at 5:44 AM, Jeffrey Walton noloa...@gmail.com wrote:
I want to use double checked initialization for a program, but I'm
catching some warnings from helgrind. A typical use is shown below.
Its kind of tedious to run --gen-suppressions=yes for to develop
suppressions. Plus,
On Sun, Aug 28, 2011 at 2:32 PM, Milian Wolff m...@milianw.de wrote:
On Saturday 27 August 2011 23:44:02 Jeffrey Walton wrote:
I want to use double checked initialization for a program, but I'm
catching some warnings from helgrind. A typical use is shown below.
Its kind of tedious to run
Thanks Bart,
On Sun, Aug 28, 2011 at 12:26 PM, Bart Van Assche bvanass...@acm.org wrote:
On Sun, Aug 28, 2011 at 6:13 PM, Jeffrey Walton noloa...@gmail.com wrote:
(1) Never trust wikipedia.
Reading your message makes me wonder whether you are familiar with the
reason why memory barriers
On Sun, Aug 28, 2011 at 6:55 PM, Jeffrey Walton noloa...@gmail.com wrote:
On Sun, Aug 28, 2011 at 12:26 PM, Bart Van Assche bvanass...@acm.org wrote:
On Sun, Aug 28, 2011 at 6:13 PM, Jeffrey Walton noloa...@gmail.com wrote:
(1) Never trust wikipedia.
Reading your message makes me wonder
