From: Samuel Thibault <samuel.thibault@gnu.org>
To: Jeff Law <law@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Coping with gcc warning due to limitation of gcc analysis?
Date: Sun, 28 Jan 2018 14:45:00 -0000 [thread overview]
Message-ID: <20180127221607.sxxu7tfjaxgo4r37@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <bf25fd3d-145e-a829-802d-4605c6c72767@redhat.com>
Jeff Law, on sam. 27 janv. 2018 14:25:29 -0700, wrote:
> On 01/27/2018 01:54 PM, Samuel Thibault wrote:
> > What is the glibc-preferred way to deal with this? Of course I could
> > just initialize saved to a dumb value like -1 but the reader might
> > wonder why unless we put a blunt comment, and a smarter compiler might
> > later warn "-1 set in `saved' is never used"...
> First, make sure you've filed a bug with a reproducer in GCC :-)
I have just filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84078
So should I set CFLAGS-getresgid.c += -Wno-error=maybe-uninitialized
?
Samuel
next prev parent reply other threads:[~2018-01-27 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 2:03 Samuel Thibault
2018-01-28 10:58 ` Jeff Law
2018-01-28 14:45 ` Samuel Thibault [this message]
2018-01-28 14:49 ` Florian Weimer
2018-01-29 18:26 ` Joseph Myers
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=20180127221607.sxxu7tfjaxgo4r37@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@gnu.org \
--cc=law@redhat.com \
--cc=libc-alpha@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).