From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: silence unused-but-set-variable warning about yynerrs in cp-name-parser.y
Date: Mon, 17 Oct 2022 08:38:53 -0400 [thread overview]
Message-ID: <49211548-0894-2374-c83f-f590be7761af@simark.ca> (raw)
In-Reply-To: <87bkqenyec.fsf@tromey.com>
On 2022-10-14 12:49, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> I initially fixed this by using
> Simon> DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE (like in commit f7aa1a5acc5
> Simon> ("gold: Suppress "unused" variable warning on Clang")), but then I
> Simon> realized we could suppress the warning in a more fine-grained way using
> Simon> this in a rule:
>
> Simon> (void) yynerrs;
>
> Seems fine to me.
>
> Tom
Pushed, thanks.
Simon
prev parent reply other threads:[~2022-10-17 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 17:32 Simon Marchi
2022-10-14 16:49 ` Tom Tromey
2022-10-17 12:38 ` Simon Marchi [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=49211548-0894-2374-c83f-f590be7761af@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=tom@tromey.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).