public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Alejandro Colomar <alx@kernel.org>,
	 Andreas Schwab <schwab@linux-m68k.org>,
	David Malcolm <dmalcolm@redhat.com>,
	 Florian Weimer <fweimer@redhat.com>,
	Iker Pedrosa <ipedrosa@redhat.com>,
	 Jens Gustedt <jens.gustedt@inria.fr>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	 Mark Wielaard <mark@klomp.org>, Martin Uecker <uecker@tugraz.at>,
	 Michael Kerrisk <mtk.manpages@gmail.com>,
	Paul Eggert <eggert@cs.ucla.edu>, Sam James <sam@gentoo.org>,
	 Siddhesh Poyarekar <siddhesh@gotplt.org>,
	Yann Droneaud <ydroneaud@opteya.com>
Subject: Re: Ping: [PATCH resend] Make -Wuse-after-free=3 the default one in -Wall
Date: Wed, 15 Mar 2023 15:52:34 +0100	[thread overview]
Message-ID: <CAFiYyc1+yR-Xq5=qZQPojsN-W+f+JMSPWxoOuNS4ExrNiZuWWw@mail.gmail.com> (raw)
In-Reply-To: <a76c2ae7-19df-847d-8f84-9b27b9c89b71@gmail.com>

On Wed, Mar 15, 2023 at 3:30 PM Alejandro Colomar via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Ping

-Wuse-after-free=3 was explicitly added to cover cases with a high
false-positive rate.  If you want to
make that the default then instead merge the equality compare case
back to the =2 case.

But as I said elsewhere I think that -Wuse-after-free is very much too
trigger happy, especially
with value-uses (not accessing released memory but inspecting the old
pointer value).  Please consider
looking at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104075 and
review the false positives
reported.

Also see my very recent patches from today trying to limit
-Wuse-after-free by not diagnosing
from late IL.

Richard.

> On 2/18/23 00:05, Alejandro Colomar wrote:
> > Link: <https://inbox.sourceware.org/gcc/3098fd18-9dbf-b4e9-bae5-62ec6fea74cd@opteya.com/T/>
> > Link: <https://github.com/shadow-maint/shadow/pull/649#discussion_r1108350066>
> > Cc: Andreas Schwab <schwab@linux-m68k.org>
> > Cc: David Malcolm <dmalcolm@redhat.com>
> > Cc: Florian Weimer <fweimer@redhat.com>
> > Cc: Iker Pedrosa <ipedrosa@redhat.com>
> > Cc: Jens Gustedt <jens.gustedt@inria.fr>
> > Cc: Jonathan Wakely <jwakely.gcc@gmail.com>
> > Cc: Mark Wielaard <mark@klomp.org>
> > Cc: Martin Uecker <uecker@tugraz.at>
> > Cc: Michael Kerrisk <mtk.manpages@gmail.com>
> > Cc: Paul Eggert <eggert@cs.ucla.edu>
> > Cc: Sam James <sam@gentoo.org>
> > Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>
> > Cc: Yann Droneaud <ydroneaud@opteya.com>
> > Signed-off-by: Alejandro Colomar <alx@kernel.org>
> > ---
> >
> > This is a resend of the same patch previously sent to gcc@.
> >
> >  gcc/c-family/c.opt  | 4 ++--
> >  gcc/doc/invoke.texi | 2 +-
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/gcc/c-family/c.opt b/gcc/c-family/c.opt
> > index c0fea56a8f5..1a3fc2c5d74 100644
> > --- a/gcc/c-family/c.opt
> > +++ b/gcc/c-family/c.opt
> > @@ -1411,11 +1411,11 @@ C ObjC C++ ObjC++ Joined RejectNegative UInteger Var(warn_unused_const_variable)
> >  Warn when a const variable is unused.
> >
> >  ; Defining this option here in addition to common.opt is necessary
> > -; in order for the default -Wall setting of -Wuse-after-free=2 to take
> > +; in order for the default -Wall setting of -Wuse-after-free=3 to take
> >  ; effect.
> >
> >  Wuse-after-free=
> > -LangEnabledBy(C ObjC C++ LTO ObjC++, Wall,2,0)
> > +LangEnabledBy(C ObjC C++ LTO ObjC++, Wall,3,0)
> >  ; in common.opt
> >
> >  Wvariadic-macros
> > diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> > index 7b308cd3c31..d910052ce0c 100644
> > --- a/gcc/doc/invoke.texi
> > +++ b/gcc/doc/invoke.texi
> > @@ -4720,7 +4720,7 @@ instead of pointers.  This approach obviates needing to adjust the stored
> >  pointers after reallocation.
> >  @end table
> >
> > -@option{-Wuse-after-free=2} is included in @option{-Wall}.
> > +@option{-Wuse-after-free=3} is included in @option{-Wall}.
> >
> >  @item -Wuseless-cast @r{(C++ and Objective-C++ only)}
> >  @opindex Wuseless-cast
>
> --
> <http://www.alejandro-colomar.es/>
> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

  reply	other threads:[~2023-03-15 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3d7d07cf-3276-b091-69d5-bf00b04e518d@gotplt.org>
2023-02-17 23:05 ` Alejandro Colomar
2023-03-15 14:30   ` Ping: " Alejandro Colomar
2023-03-15 14:52     ` Richard Biener [this message]
2023-03-15 15:13       ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFiYyc1+yR-Xq5=qZQPojsN-W+f+JMSPWxoOuNS4ExrNiZuWWw@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=dmalcolm@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ipedrosa@redhat.com \
    --cc=jens.gustedt@inria.fr \
    --cc=jwakely.gcc@gmail.com \
    --cc=mark@klomp.org \
    --cc=mtk.manpages@gmail.com \
    --cc=sam@gentoo.org \
    --cc=schwab@linux-m68k.org \
    --cc=siddhesh@gotplt.org \
    --cc=uecker@tugraz.at \
    --cc=ydroneaud@opteya.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).