public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] hurd: Avoid spurious warning
Date: Tue,  3 Aug 2021 17:38:58 +0000 (GMT)	[thread overview]
Message-ID: <20210803173858.2F60F3858D39@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=df183287ff7ded9471205abfa59df27e5e5401da

commit df183287ff7ded9471205abfa59df27e5e5401da
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Tue Aug 3 19:37:43 2021 +0200

    hurd: Avoid spurious warning
    
    Compilers missing some flow analysis may think ss may be used
    uninitialized.

Diff:
---
 hurd/hurdselect.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hurd/hurdselect.c b/hurd/hurdselect.c
index 9790d54864..cab23fdd82 100644
--- a/hurd/hurdselect.c
+++ b/hurd/hurdselect.c
@@ -67,7 +67,7 @@ _hurd_select (int nfds,
       int error;
     } d[nfds];
   sigset_t oset;
-  struct hurd_sigstate *ss;
+  struct hurd_sigstate *ss = NULL;
 
   union typeword		/* Use this to avoid unkosher casts.  */
     {


                 reply	other threads:[~2021-08-03 17:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210803173858.2F60F3858D39@sourceware.org \
    --to=sthibaul@sourceware.org \
    --cc=glibc-cvs@sourceware.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).