This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Coping with gcc warning due to limitation of gcc analysis?

From: Samuel Thibault <samuel dot thibault at gnu dot org>
To: Jeff Law <law at redhat dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Sat, 27 Jan 2018 23:16:07 +0100
Subject: Re: Coping with gcc warning due to limitation of gcc analysis?
Authentication-results: sourceware.org; auth=none
References: <20180127205417.4eruhvizwf4x2y2c@var.youpi.perso.aquilenet.fr> <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

References:
- Coping with gcc warning due to limitation of gcc analysis?
  - From: Samuel Thibault
- Re: Coping with gcc warning due to limitation of gcc analysis?
  - From: Jeff Law

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]