public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, msebor@redhat.com
Subject: Re: [PATCH] -Wdangling-pointer: don't mark SSA lhs sets as stores
Date: Fri, 3 Mar 2023 12:12:37 +0100	[thread overview]
Message-ID: <CAFiYyc0XeTfoXompiGM4BfzjS+rx64iZJWH0Ot6YLowJeiM3cw@mail.gmail.com> (raw)
In-Reply-To: <orcz5qjkxx.fsf@lxoliva.fsfla.org>

On Fri, Mar 3, 2023 at 9:30 AM Alexandre Oliva <oliva@adacore.com> wrote:
>
> On Feb 17, 2023, Richard Biener <richard.guenther@gmail.com> wrote:
>
> >> * gimple-ssa-warn-access.cc
> >> (pass_waccess::check_dangling_stores): Skip non-stores.
> >>
> >> for  gcc/testsuite/ChangeLog
> >>
> >> * g++.dg/warn/Wdangling-pointer.C (warn_init_ref_member): Add
> >> two new variants, one fixed, one xfailed.
> >> * c-c++-common/Wdangling-pointer-5.c
> >> (nowarn_store_arg_store_arg): Add now-expected warnings.
>
> Ping?
> https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612186.html

I was hoping Martin would chime in, but he didn't.

So - OK.

Thanks,
Richard.

>
> --
> Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
>    Free Software Activist                       GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts.  Ask me about <https://stallmansupport.org>

  reply	other threads:[~2023-03-03 11:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  7:09 Alexandre Oliva
2023-02-17  7:53 ` Richard Biener
2023-02-17  8:35   ` Alexandre Oliva
2023-02-17  9:09     ` Alexandre Oliva
2023-03-03  8:30   ` Alexandre Oliva
2023-03-03 11:12     ` Richard Biener [this message]
2023-03-08 13:04       ` Martin Liška
2023-03-08 13:08         ` Richard Biener
2023-03-09  8:23           ` Alexandre Oliva

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=CAFiYyc0XeTfoXompiGM4BfzjS+rx64iZJWH0Ot6YLowJeiM3cw@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=msebor@redhat.com \
    --cc=oliva@adacore.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).