From: Alejandro Colomar <alx.manpages@gmail.com>
To: Richard Biener <richard.guenther@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 16:13:28 +0100 [thread overview]
Message-ID: <a3f0a244-4107-e251-c186-b0330bd057d2@gmail.com> (raw)
In-Reply-To: <CAFiYyc1+yR-Xq5=qZQPojsN-W+f+JMSPWxoOuNS4ExrNiZuWWw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
Hi Richard,
On 3/15/23 15:52, Richard Biener wrote:
> 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.
Hmmm, thanks, didn't know about those. Please ignore my patch.
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-03-15 15:13 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
2023-03-15 15:13 ` Alejandro Colomar [this message]
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=a3f0a244-4107-e251-c186-b0330bd057d2@gmail.com \
--to=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=richard.guenther@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).