From: Jeff Law <law@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
gcc-patches@gcc.gnu.org, bkorb@gnu.org
Subject: Re: [PATCH] fixincludes/fixfixes.c: Fix 'set but not used' warning.
Date: Wed, 16 Sep 2020 22:16:09 -0600 [thread overview]
Message-ID: <44d8585a-5e25-dbeb-7dbe-cef16fa8374e@redhat.com> (raw)
In-Reply-To: <1599826919-5148-1-git-send-email-christophe.lyon@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On 9/11/20 6:21 AM, Christophe Lyon via Gcc-patches wrote:
> pz_tmp_base and pz_tmp_dot are always set, but used only when
> _PC_NAME_MAX is defined.
>
> This patch moves their declaration and definition undef #ifdef
> _PC_NAME_MAX to avoid this warning.
>
> 2020-09-11 Torbjörn SVENSSON <torbjorn.svensson@st.com>
> Christophe Lyon <christophe.lyon@linaro.org>
>
> fixincludes/
> * fixfixes.c (pz_tmp_base, pz_tmp_dot): Define only with
> _PC_NAME_MAX.
OK. I assume Christophe can commit the change.
Jeff
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1763 bytes --]
next prev parent reply other threads:[~2020-09-17 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:21 Christophe Lyon
2020-09-17 4:16 ` Jeff Law [this message]
2020-09-17 9:37 ` Christophe Lyon
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=44d8585a-5e25-dbeb-7dbe-cef16fa8374e@redhat.com \
--to=law@redhat.com \
--cc=bkorb@gnu.org \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@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).