public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17307] Spurious -Wsign-conversion warning with clang-3.5, due to excessively clever glibc <sys/resource.h>
Date: Mon, 25 Aug 2014 17:40:00 -0000 [thread overview]
Message-ID: <bug-17307-131-M6qNh8TpyN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17307-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17307
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
The first question I have is: Does this trigger a gcc warning with new enough
gcc. If it does then we're in trouble and likely need to remove our cleverness.
If it doesn't then it would be good to talk with clang developers to see if we
can do some kind of whitelist to make this all work. The implementation is
certainly OK to collude on these things as long as we all move forward in the
right direction and can agree on that direction.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-08-25 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 14:36 [Bug libc/17307] New: " zackw at panix dot com
2014-08-25 17:40 ` carlos at redhat dot com [this message]
2014-08-25 18:54 ` [Bug libc/17307] " zackw at panix dot com
2014-08-26 3:54 ` bugdal at aerifal dot cx
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=bug-17307-131-M6qNh8TpyN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).