From: Jakub Jelinek <jakub@redhat.com>
To: JonY <10walls@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
NightStrike <nightstrike@gmail.com>
Subject: Re: [PATCH] Suppress ssp.c unused variable warning on mingw
Date: Sat, 01 Apr 2017 07:07:00 -0000 [thread overview]
Message-ID: <20170401070733.GS17461@tucnak> (raw)
In-Reply-To: <9c34a6b6-c4d2-2444-685d-7a8b7be74da0@gmail.com>
On Sat, Apr 01, 2017 at 03:35:35AM +0000, JonY wrote:
> This suppresses an unused variable warning for mingw*, patch OK?
Ok.
> Index: libssp/ssp.c
> ===================================================================
> --- libssp/ssp.c (revision 246630)
> +++ libssp/ssp.c (working copy)
> @@ -72,7 +72,6 @@
> __guard_setup (void)
> {
> unsigned char *p;
> - int fd;
>
> if (__stack_chk_guard != 0)
> return;
> @@ -91,7 +90,7 @@
> CryptReleaseContext(hprovider, 0);
> }
> #else
> - fd = open ("/dev/urandom", O_RDONLY);
> + int fd = open ("/dev/urandom", O_RDONLY);
> if (fd != -1)
> {
> ssize_t size = read (fd, &__stack_chk_guard,
>
>
> Changelog:
> 2017-04-01 Jonathan Yong <10walls@gmail.com>
>
> * ssp.c (__guard_setup): Suppress unused variable warning.
>
>
Jakub
prev parent reply other threads:[~2017-04-01 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 3:41 JonY
2017-04-01 7:07 ` Jakub Jelinek [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=20170401070733.GS17461@tucnak \
--to=jakub@redhat.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.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).