[llvm-dev] Full restrict support - status update

[Roman Lebedev via llvm-dev]

On Tue, Oct 29, 2019 at 9:26 PM David Greene via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> 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.
Yes :)
I would think it would not require any runtime (think - asan/msan) support,
so i'm not sure why it could not be a part of UBSan proper.
In other words i'd like to *tentatively* claim this,
i may be interested to look into it, after the restrict support lands :)

>                       -David
Roman

> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev