On Fri, 7 Feb 2020, Richard Biener wrote:
> To me it's a QOI question that depends on the actual case.
> Turning memcpy (p, p, N) into a no-op is the correct thing,
> even though with (too) large N it might trap. Folding
> a read from outside of an object to zero might be OK
> (it's undefined), b
On Thu, 2020-02-06 at 14:16 +0100, Richard Biener wrote:
> On Thu, Feb 6, 2020 at 2:00 PM Jeff Law wrote:
> > On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> > > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > > > On 2/4/20 2:31 PM, Jeff Law wrote:
> > > > > On Tue, 2020-02-04
On Fri, Feb 7, 2020 at 12:08 AM Martin Sebor wrote:
>
> On 2/6/20 6:16 AM, Richard Biener wrote:
> > On Thu, Feb 6, 2020 at 2:00 PM Jeff Law wrote:
> >>
> >> On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> >>> On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> On 2/4/20 2:31 P
On 2/6/20 6:16 AM, Richard Biener wrote:
On Thu, Feb 6, 2020 at 2:00 PM Jeff Law wrote:
On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
On 2/4/20 2:31 PM, Jeff Law wrote:
On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
On
On Thu, Feb 6, 2020 at 2:00 PM Jeff Law wrote:
>
> On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > > On 2/4/20 2:31 PM, Jeff Law wrote:
> > > > On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> > > > > On 2/4/20 12:15 PM,
On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > On 2/4/20 2:31 PM, Jeff Law wrote:
> > > On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> > > > On 2/4/20 12:15 PM, Richard Biener wrote:
> > > > > On February 4, 2020 5:30:42
On Thu, Feb 6, 2020 at 12:14 PM Richard Biener
wrote:
>
> On Thu, Feb 6, 2020 at 11:33 AM Richard Biener
> wrote:
> >
> > On Thu, Feb 6, 2020 at 11:06 AM Richard Biener
> > wrote:
> > >
> > > On Wed, Feb 5, 2020 at 4:55 PM Martin Sebor wrote:
> > > >
> > > > On 2/5/20 1:19 AM, Richard Biener wr
On Thu, Feb 6, 2020 at 11:33 AM Richard Biener
wrote:
>
> On Thu, Feb 6, 2020 at 11:06 AM Richard Biener
> wrote:
> >
> > On Wed, Feb 5, 2020 at 4:55 PM Martin Sebor wrote:
> > >
> > > On 2/5/20 1:19 AM, Richard Biener wrote:
> > > > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > > >>
On Thu, Feb 6, 2020 at 11:06 AM Richard Biener
wrote:
>
> On Wed, Feb 5, 2020 at 4:55 PM Martin Sebor wrote:
> >
> > On 2/5/20 1:19 AM, Richard Biener wrote:
> > > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > >>
> > >> On 2/4/20 2:31 PM, Jeff Law wrote:
> > >>> On Tue, 2020-02-04 at 1
On Wed, Feb 5, 2020 at 4:55 PM Martin Sebor wrote:
>
> On 2/5/20 1:19 AM, Richard Biener wrote:
> > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> >>
> >> On 2/4/20 2:31 PM, Jeff Law wrote:
> >>> On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> On 2/4/20 12:15 PM, Richard Bien
On 2/5/20 1:19 AM, Richard Biener wrote:
On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
On 2/4/20 2:31 PM, Jeff Law wrote:
On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
On 2/4/20 12:15 PM, Richard Biener wrote:
On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
On Tue
On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
>
> On 2/4/20 2:31 PM, Jeff Law wrote:
> > On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> >> On 2/4/20 12:15 PM, Richard Biener wrote:
> >>> On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law
> >>> wrote:
> On Tue, 2020-02-04 at
On 2/4/20 2:31 PM, Jeff Law wrote:
On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
On 2/4/20 12:15 PM, Richard Biener wrote:
On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor
On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> On 2/4/20 12:15 PM, Richard Biener wrote:
> > On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
> > > On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
> > > > On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
> > > > > PR 9
On 2/4/20 12:15 PM, Richard Biener wrote:
On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
PR 93519 reports a false positive -Wrestrict issued for an inlined
call
to strcpy
On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
>On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
>> On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
>> > PR 93519 reports a false positive -Wrestrict issued for an inlined
>call
>> > to strcpy that carefully guards against self
On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
> On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
> > PR 93519 reports a false positive -Wrestrict issued for an inlined call
> > to strcpy that carefully guards against self-copying. This is caused
> > by the caller's arguments substitu
On 2/4/20 2:34 AM, Richard Biener wrote:
On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
PR 93519 reports a false positive -Wrestrict issued for an inlined call
to strcpy that carefully guards against self-copying. This is caused
by the caller's arguments substituted into the call during i
On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
>
> PR 93519 reports a false positive -Wrestrict issued for an inlined call
> to strcpy that carefully guards against self-copying. This is caused
> by the caller's arguments substituted into the call during inlining and
> before dead code elimin
PR 93519 reports a false positive -Wrestrict issued for an inlined call
to strcpy that carefully guards against self-copying. This is caused
by the caller's arguments substituted into the call during inlining and
before dead code elimination.
The attached patch avoids this by removing -Wrestrict
20 matches
Mail list logo