[llvm-dev] Full restrict support - status update
David Greene via llvm-dev
llvm-dev at lists.llvm.org
Tue Oct 29 11:25:34 PDT 2019
Jeroen Dobbelaere via llvm-dev <llvm-dev at lists.llvm.org> writes:
> - the 'SingleSource/Regression/C/gcc-c-torture/execute/GCC-C-execute-pr38212.test' in the 'test-suite' fails:
> -- the test is wrong as it triggers undefined behavior: it reads and writes the same object through 2 different
> restrict pointers which have been declared in the same scope.
What's the failure mode? Wrong answers or compiler abort? If the
latter, it would be nice if LLVM could emit a warning about illegal use
of restrict. Longer term, a RestrictSanitizer would be really helpful.
More information about the llvm-dev