From: Richard Biener <richard.guenther@gmail.com>
To: priour.be@gmail.com
Cc: gcc-patches@gcc.gnu.org, dmalcolm@redhat.com,
benjamin priour <vultkayn@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: Remove unused dg-line in ce8cdf5bcf96a2db6d7b9f656fc9ba58d7942a83
Date: Thu, 17 Aug 2023 10:41:19 +0200 [thread overview]
Message-ID: <CAFiYyc3RJ0FtYQretf9xf10DmcyEpF5uOiWxW-LiMfAG_vu9fA@mail.gmail.com> (raw)
In-Reply-To: <20230815183208.330060-1-vultkayn@gcc.gnu.org>
On Tue, Aug 15, 2023 at 8:36 PM Benjamin Priour via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> From: benjamin priour <vultkayn@gcc.gnu.org>
>
> Yet another blunder.
>
> Succesfully regstrapped against ce8cdf5bcf96a2db6d7b9f656fc9ba58d7942a83
> on x86_64-linux-gnu.
>
> OK to push on trunk ?
OK.
> Sorry,
> Benjamin.
>
> Fixup below.
> ---
>
> Test case g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C
> introduced by patch ce8cdf5bcf96a2db6d7b9f656fc9ba58d7942a83
> emitted a warning for an unused dg-line variable.
> This fixes up the blunder.
>
> Signed-off-by: benjamin priour <vultkayn@gcc.gnu.org>
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C:
> Remove dg-line var declare_a.
> ---
> .../g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C b/gcc/testsuite/g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C
> index 4cc93d129f0..aa964f93563 100644
> --- a/gcc/testsuite/g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C
> +++ b/gcc/testsuite/g++.dg/analyzer/fanalyzer-show-events-in-system-headers.C
> @@ -6,7 +6,7 @@
> struct A {int x; int y;};
>
> int main () { /* { dg-message "\\(1\\) entry to 'main'" "telltale event that we are going within a deeper frame than 'main'" } */
> - std::shared_ptr<A> a; /* { dg-line declare_a } */
> + std::shared_ptr<A> a;
> a->x = 4; /* { dg-line deref_a } */
> /* { dg-warning "dereference of NULL" "" { target *-*-* } deref_a } */
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-08-17 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 18:32 priour.be
2023-08-17 8:41 ` Richard Biener [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=CAFiYyc3RJ0FtYQretf9xf10DmcyEpF5uOiWxW-LiMfAG_vu9fA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=priour.be@gmail.com \
--cc=vultkayn@gcc.gnu.org \
/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).