Lock don't hurt anyway.
May be i am not right, but i think there was some simple instructions
(not only incl) that force lock before them in both cases.
> Even if it would lock on the bus it wouldn't matter. C only knows about
> signle threading. So as far as C is concerned it's fine if it doesn't use
> incl for incrementing volatile variables IMHO.
I think so. The RISC-ifing make gcc optimize it as read, inc, write...
But this tread become pointless ;-))
regards,
Petkan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/