public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
	Steve Ellcey <sje@cup.hp.com>,
	       Richard Guenther <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org,        sterling@tensilica.com,
	rdsandiford@googlemail.com
Subject: Re: -mfused-madd vs -ffp-contract deprication?
Date: Tue, 09 Nov 2010 15:49:00 -0000	[thread overview]
Message-ID: <4CD96CD5.20806@redhat.com> (raw)
In-Reply-To: <g4eiauyjat.fsf@richards-desktop.stglab.manchester.uk.ibm.com>

On 11/09/2010 12:48 AM, Richard Sandiford wrote:
> I think they should still be conditional on TARGET_FUSED_MADD
> because of the R8000 case.  If anyone is still using bleeding edge
> GCC on R8000, we might as well continue to provide a way for them
> to disable the fusing.

Fair enough, I suppose.  Though the plan is to move away 
from -mfused-add to -ffp-contract, so a tiny bit of global
substitution will be needed.

r~

  reply	other threads:[~2010-11-09 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 13:35 [PATCH] FMA on trees Richard Guenther
2010-11-02 15:40 ` Richard Henderson
2010-11-03 13:13   ` Richard Guenther
2010-11-03 15:30     ` Richard Guenther
2010-11-08 19:23       ` Steve Ellcey
2010-11-08 19:27         ` -mfused-madd vs -ffp-contract deprication? Richard Henderson
2010-11-08 23:14           ` Joseph S. Myers
2010-11-09  1:41             ` Richard Henderson
2010-11-09  9:09               ` Richard Sandiford
2010-11-09 15:49                 ` Richard Henderson [this message]
2010-11-09  9:53           ` Richard Guenther
2010-11-09 17:14             ` Richard Henderson

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=4CD96CD5.20806@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=rdsandiford@googlemail.com \
    --cc=rguenther@suse.de \
    --cc=sje@cup.hp.com \
    --cc=sterling@tensilica.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).