On 01/11/2018 04:49 PM, Martin Sebor wrote:
> On 01/11/2018 04:24 PM, Jeff Law wrote:
>> On 01/10/2018 01:26 PM, Martin Sebor wrote:
>>> To avoid issuing duplicate warnings for the same function call
>>> in the source code the -Wrestrict warning code makes sure
>>> the no-warning bit is propagated
On 01/11/2018 04:24 PM, Jeff Law wrote:
On 01/10/2018 01:26 PM, Martin Sebor wrote:
To avoid issuing duplicate warnings for the same function call
in the source code the -Wrestrict warning code makes sure
the no-warning bit is propagated between trees and GIMPLE and
tested before issuing a warni
On 01/10/2018 01:26 PM, Martin Sebor wrote:
> To avoid issuing duplicate warnings for the same function call
> in the source code the -Wrestrict warning code makes sure
> the no-warning bit is propagated between trees and GIMPLE and
> tested before issuing a warning. But the warning also detects
>
To avoid issuing duplicate warnings for the same function call
in the source code the -Wrestrict warning code makes sure
the no-warning bit is propagated between trees and GIMPLE and
tested before issuing a warning. But the warning also detects
some of the same problems as -Wstringop-overflow, an
