Re: [PING] [PATCH] avoid -Wrestrict for null pointers (PR 85365)

2018-04-20 Thread Richard Biener
On Thu, Apr 19, 2018 at 6:05 PM, Martin Sebor  wrote:
> Ping: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00676.html
>
> Testing on x86_64-linux showed no regressions.

OK.

Richard.

>
> On 04/13/2018 10:49 AM, Martin Sebor wrote:
>>
>> PR 85365 is another example of a false positive caused by
>> the interaction between the instrumentation inserted by
>> sanitizers, jump threading, and a middle-end warning.
>> In this case, the warning is easy to avoid by suppressing
>> -Wrestrict for null pointers.  Although undefined, since
>> they do no point to an object, strictly speaking they do
>> not indicate an overlap, and so issuing a -Wrestrict
>> warning is not quite appropriate anyway.
>>
>> Testing in progress.
>>
>> Martin
>
>


[PING] [PATCH] avoid -Wrestrict for null pointers (PR 85365)

2018-04-19 Thread Martin Sebor

Ping: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00676.html

Testing on x86_64-linux showed no regressions.

On 04/13/2018 10:49 AM, Martin Sebor wrote:

PR 85365 is another example of a false positive caused by
the interaction between the instrumentation inserted by
sanitizers, jump threading, and a middle-end warning.
In this case, the warning is easy to avoid by suppressing
-Wrestrict for null pointers.  Although undefined, since
they do no point to an object, strictly speaking they do
not indicate an overlap, and so issuing a -Wrestrict
warning is not quite appropriate anyway.

Testing in progress.

Martin