Link: Threads Cannot be Implemented as a Library

January 1, 2007

I've already linked to this in passing, but I'm going to rerun it as an explicit link. Threads Cannot be Implemented as a Library by Hans Boehm makes the argument in its title:

We provide specific arguments that a pure library approach, in which the compiler is designed independently of threading issues, cannot guarantee correctness of the resulting code.

There is also a discussion of this paper at Lambda the Ultimate that may be interesting reading. On a quick skim of the LtU discussion thread, this Usenet article jumps out as a useful summary of the entire volatile and multiprocessor programming issue, ending up with the conclusion that using volatile is both unnecessary and harmful in shared-state concurrent programming.


Comments on this page:

From 71.141.225.199 at 2007-01-02 00:40:16:

This is a pretty famous thing about how java's memory model was originaly broken:

http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html

--nothings

Written on 01 January 2007.
« A (Solaris 8) automounter irritation
Solaris's impressive ABI compatibility »

Page tools: View Source, View Normal, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Mon Jan 1 22:14:53 2007
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.