From: Richard Henderson <rth@redhat.com>
To: joseph@codesourcery.com
Cc: Steve Ellcey <sje@cup.hp.com>,
Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org
Subject: -mfused-madd vs -ffp-contract deprication?
Date: Mon, 08 Nov 2010 19:27:00 -0000 [thread overview]
Message-ID: <4CD84DCB.5080806@redhat.com> (raw)
In-Reply-To: <201011081911.oA8JBqS23929@lucas.cup.hp.com>
On 11/08/2010 11:11 AM, Steve Ellcey wrote:
> This patch seems to have broken -mno-fused-madd on IA64. I don't
> know if it has broken it on other platforms too.
Probably.
I wonder about making -mfused-madd a generic alias for -ffp-contract,
and removing it from the backends. With an appropriate warning, we
ought to be able to remove -mfused-madd in gcc 4.7.
r~
next prev parent reply other threads:[~2010-11-08 19:23 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 ` Richard Henderson [this message]
2010-11-08 23:14 ` -mfused-madd vs -ffp-contract deprication? Joseph S. Myers
2010-11-09 1:41 ` Richard Henderson
2010-11-09 9:09 ` Richard Sandiford
2010-11-09 15:49 ` Richard Henderson
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=4CD84DCB.5080806@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
--cc=sje@cup.hp.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).