public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jay dot krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44308] ranlib: file: libbackend
Date: Sun, 30 May 2010 08:07:00 -0000 [thread overview]
Message-ID: <20100530080646.17627.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44308-16543@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from jay dot krell at cornell dot edu 2010-05-30 08:06 -------
I understand it is "ok".
Question is: Do you want to be warning free?
At what cost?
I think you do, at some finite cost, and I think the change is worthwhile here.
This isn't adding symbols at random, it is adding them in a small safe way that
fixes the warnings, leading more configurations, common ones, to be
warning-free.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44308
next prev parent reply other threads:[~2010-05-30 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 11:10 [Bug c/44308] New: " jay dot krell at cornell dot edu
2010-05-28 13:06 ` [Bug middle-end/44308] " steven at gcc dot gnu dot org
2010-05-30 8:07 ` jay dot krell at cornell dot edu [this message]
2010-05-30 8:56 ` jay dot krell at cornell dot edu
2010-05-31 12:15 ` jay dot krell at cornell dot edu
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=20100530080646.17627.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).