Patrick Elliott wrote:
> 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. ;-)

-- 
   Darren New, San Diego CA, USA (PST)
   "We'd like you to back-port all the changes in 2.0
    back to version 1.0."
   "We've done that already. We call it 2.0."

Post a reply to this message