On 1 August 2013 17:18, Bennie Kloosteman <[email protected]> wrote: > Single threaded ie no concurrency is an option for concurrency - right ? > And these still achieve concurrency eg multiple node.js servers on a > single machine. It just has nothing to do with the language / runtime..
At least, in any discussion of optimising code for the concurrency mechanism used, it deserves consideration. If the compiler knows that the program is single-threaded, a lot of the preconditions for optimisation get a lot simpler. OTOH, even in the architectures that are not cache-coherent, the memory model is usually strict enough to get you most of what you want. Which is to say, locks and full memory barriers are probably needed a lot less than the defensive runtime architect probably imagines, especially if you're used to targetting C. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely may reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to deny you those rights would be illegal without prior contractual agreement. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
