AspectC++ fails to build in parallel on kFreeBSD due to a corrupted file which is accessed concurrently during build. Reinhard told me hs traced it down to some [0] non-functional syncronization primitive.
...
[0] Forgot the name again I'm horribly bad at remembering those shortened C identifiers.
...
maybe we have some problem in glibc here?
Do you have a test case ? The current gcc is more agressive in reordering, may be we miss some clobber in inline asm somewhere. Petr -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
