public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: Steve Ellcey <sellcey@imgtec.com>,
	       Richard Sandiford <richard.sandiford@arm.com>,
	       Joseph Myers <joseph@codesourcery.com>,
	       gcc-patches@gcc.gnu.org,
	Catherine Moore <clm@codesourcery.com>,
	       Matthew Fortune <matthew.fortune@imgtec.com>
Subject: Re: [Patch, MIPS] Enable fp-contract on MIPS and update -mfused-madd
Date: Thu, 18 Jun 2015 12:04:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.11.1506181252400.16441@eddie.linux-mips.org> (raw)
In-Reply-To: <87381qw4wz.fsf@googlemail.com>

On Wed, 17 Jun 2015, Richard Sandiford wrote:

> and the one mips-ps-3d.md:
> 
> (define_expand "mips_abs_ps"
>   [(set (match_operand:V2SF 0 "register_operand")
> 	(unspec:V2SF [(match_operand:V2SF 1 "register_operand")]
> 		     UNSPEC_ABS_PS))]
>   "TARGET_HARD_FLOAT && TARGET_PAIRED_SINGLE_FLOAT"
> {
>   /* If we can ignore NaNs, this operation is equivalent to the
>      rtl ABS code.  */
>   if (!HONOR_NANS (V2SFmode))
>     {
>       emit_insn (gen_absv2sf2 (operands[0], operands[1]));
>       DONE;
>     }
> })

 Hmm, I wonder whether this one shouldn't really be:

   if (mips_abs == MIPS_IEEE_754_2008 || !HONOR_NANS (V2SFmode))

as even though not explicitly specified for an ABS2008 implementation 
that also supports the MIPS-3D ASE, I'd say ABS.PS is supposed to be 
consistent with ABS.D and ABS.S and respect FCSR.ABS2008.

  Maciej

  parent reply	other threads:[~2015-06-18 12:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 20:09 Steve Ellcey 
2015-06-11 20:39 ` Joseph Myers
2015-06-15 20:52   ` Maciej W. Rozycki
2015-06-15 21:37     ` Joseph Myers
2015-06-15 22:00       ` Maciej W. Rozycki
2015-06-15 22:09         ` Joseph Myers
2015-06-16 12:19           ` Maciej W. Rozycki
2015-06-16 12:26             ` Joseph Myers
2015-06-16 13:28               ` Maciej W. Rozycki
2015-06-16 16:13                 ` Joseph Myers
2015-06-17 10:43                 ` Richard Sandiford
2015-06-17 17:45                   ` Steve Ellcey
2015-06-17 18:44                     ` Maciej W. Rozycki
2015-06-17 18:52                       ` Richard Sandiford
2015-06-17 21:09                         ` Steve Ellcey
2015-06-17 22:06                           ` Matthew Fortune
2015-06-18 12:32                             ` Maciej W. Rozycki
2015-06-18 16:02                               ` Steve Ellcey
2015-06-29 16:10                                 ` Maciej W. Rozycki
2015-06-29 19:07                                   ` Matthew Fortune
2015-06-29 19:46                                     ` Moore, Catherine
2015-07-06 17:35                                     ` Steve Ellcey
2015-06-30  7:35                                   ` Richard Biener
2015-06-18 12:04                         ` Maciej W. Rozycki [this message]
2015-06-17 19:51                       ` Steve Ellcey

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=alpine.LFD.2.11.1506181252400.16441@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=clm@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=matthew.fortune@imgtec.com \
    --cc=rdsandiford@googlemail.com \
    --cc=richard.sandiford@arm.com \
    --cc=sellcey@imgtec.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).