[llvm-dev] Full restrict support - status update

Sam Elliott via llvm-dev
Tue, 29 Oct 2019 17:01:57 -0000

> On 29 Oct 2019, at 4:06 am, Finkel, Hal J. via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>
> On 10/28/19 8:12 PM, Jeroen Dobbelaere via llvm-dev wrote:
>>
>> - 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.
>
>
> This, we can fix now independent of anything else. We should either fix
> the test, if there's a reasonable way to fix it, or we should remove
it.
> If you can post a patch with an explanation of the problem, that would
> be great.

I’m wary of updating the test itself, as someone may re-vendor the GCC C torture
suite, undoing those edits. However, we already exclude some tests in the GCC
torture suite because they rely on UB. Having inspected pr38212.c, I am happy to
add this test to the list of excluded tests with the explanation provided. I’ll
commit that change today.

Sam

--
Sam Elliott
Software Developer - LLVM
lowRISC CIC
--