From: Richard Sandiford <rdsandiford@googlemail.com>
To: Jim Wilson <wilson@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, MIPS] .gnu.attribute support for sdemtk -mno-float
Date: Thu, 20 May 2010 22:32:00 -0000 [thread overview]
Message-ID: <87fx1muse6.fsf@firetop.home> (raw)
In-Reply-To: <1274337969.2656.74.camel@localhost> (Jim Wilson's message of "Wed, 19 May 2010 23:46:09 -0700")
Jim Wilson <wilson@codesourcery.com> writes:
> On Sat, 2010-05-08 at 17:55 +0100, Richard Sandiford wrote:
>> However, I don't like the idea of hiding the option behind even more
>> hooks. I'd prefer to expose TARGET_NO_FLOAT to the generic code instead.
>> Any objections to the following alternative? Tested on mipsisa64-elf
>> and by inspection on mipsisa64-sde-elf.
>
> No objections. This looks fine to me.
Thanks, applied.
Richard
prev parent reply other threads:[~2010-05-20 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 2:47 Jim Wilson
2010-05-01 8:18 ` Richard Sandiford
2010-05-03 20:20 ` Jim Wilson
2010-05-08 16:56 ` Richard Sandiford
2010-05-20 7:00 ` Jim Wilson
2010-05-20 22:32 ` Richard Sandiford [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=87fx1muse6.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=wilson@codesourcery.com \
/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).