>> The compiler needs to be smart enough to "know" you are compiling for 
>> multi-cores, and warn you about such things (or avoid optimizing in a 
>> way that causes them).
> 
> More precisely, the compiler needs to "know" what your processes are, 
> instead of leaving it as an opaque library outside the semantics of the 
> language completely. See the ongoing thread elsewhere. ;-)

And I would suggest that geniunely "high-level" languages (i.e., 
languages were you don't manually frob low-level machine resources) have 
a much greater chance of adapting to multicore programming...

Post a reply to this message