From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: Fix warnings from MIPS soft-float _FPU_GETCW
Date: Wed, 05 Dec 2012 15:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1212051521590.1819@digraph.polyomino.org.uk> (raw)
In-Reply-To: <50BF64FC.9020000@tilera.com>
On Wed, 5 Dec 2012, Chris Metcalf wrote:
> I see the same warning on tile, because we are using
> sysdeps/generic/fpu_control.h, which has the same issue. Do you want to
> fix that file as well as the mips one while you're at it? Or should I
> push that same fix?
If you observe warnings on an architecture you are testing and have a
patch to fix those warnings, please post the patch as usual (to libc-alpha
in this case). In general architecture maintainers should be reviewing
warning state, as well as test results, for their architectures for 2.17
and trying to get both into good shape for the release.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2012-12-05 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 22:08 Joseph S. Myers
2012-12-05 15:15 ` Chris Metcalf
2012-12-05 15:23 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.1212051521590.1819@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmetcalf@tilera.com \
--cc=libc-ports@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).