On 08/10/2018, 13:50, "Jerin Jacob" <jerin.ja...@caviumnetworks.com> wrote:
I don't know how that creates more undefined behavior. So replied in the
context of your reply that, according to your view even Linux is running
with undefined behavior.
As I explained, Linux does not use C11 atomics (nor GCC __atomic builtins) so
cannot express the kind of undefined behaviour caused by mixing conflicting
atomic
(as defined by the C11 standard) and non-atomic accesses to the same object.
Checked the latest version from https://github.com/torvalds/linux
