From: Florian Weimer <fw@deneb.enyo.de>
To: Samuel Thibault <samuel.thibault@gnu.org>
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:49:00 -0000 [thread overview]
Message-ID: <87r2qbhr4z.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20180127205417.4eruhvizwf4x2y2c@var.youpi.perso.aquilenet.fr> (Samuel Thibault's message of "Sat, 27 Jan 2018 21:54:17 +0100")
* Samuel Thibault:
> What is the glibc-preferred way to deal with this?
The preferred way is to rewrite the code to make it clearer. For
__getresgid, that would probably involve writing to *rgid, *egid,
*sgid directly, without relying on the temporary variables.
For cases where this is not possible, there are the
DIAG_PUSH_NEEDS_COMMENT, DIAG_IGNORE_NEEDS_COMMENT,
DIAG_POP_NEEDS_COMMENT macros.
next prev parent reply other threads:[~2018-01-27 22:29 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
2018-01-28 14:49 ` Florian Weimer [this message]
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=87r2qbhr4z.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@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).