From: Richard Biener <richard.guenther@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: David Sherwood <david.sherwood@arm.com>,GCC Patches
<gcc-patches@gcc.gnu.org>,richard.sandiford@arm.com
Subject: Re: [PING][Patch] Add support for IEEE-conformant versions of scalar fmin* and fmax*
Date: Wed, 19 Aug 2015 15:25:00 -0000 [thread overview]
Message-ID: <D248FF31-2CB2-496B-A732-254ECF34A905@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1508191704220.30229@wotan.suse.de>
On August 19, 2015 5:05:01 PM GMT+02:00, Michael Matz <matz@suse.de> wrote:
>Hi,
>
>On Wed, 19 Aug 2015, Richard Biener wrote:
>
>> I think tree_code is 64bits now.
>
>Huh? No; it's 16 bit since 8 bit run out.
Err, that's what I was trying to say...
16bits, obviously.
BTW, in addition to errno math there is rounding math where we rely on virtual operands to not mess with ordering.
Richard.
>
>Ciao,
>Michael.
next prev parent reply other threads:[~2015-08-19 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 10:13 David Sherwood
2015-08-13 11:12 ` Richard Biener
2015-08-17 9:41 ` David Sherwood
2015-08-17 14:02 ` Richard Biener
2015-08-18 11:10 ` David Sherwood
2015-08-18 13:31 ` Richard Biener
2015-08-18 14:20 ` Richard Sandiford
2015-08-19 9:48 ` Richard Biener
2015-08-19 10:04 ` Richard Sandiford
2015-08-19 10:31 ` Richard Biener
2015-08-19 12:23 ` Richard Sandiford
2015-08-19 12:35 ` Richard Biener
2015-08-19 13:16 ` Richard Sandiford
2015-08-19 13:41 ` Richard Biener
2015-09-14 10:47 ` David Sherwood
2015-09-14 13:42 ` Richard Biener
2015-09-14 20:38 ` Joseph Myers
2015-08-19 15:32 ` Joseph Myers
2015-11-23 9:21 ` David Sherwood
2015-11-25 12:39 ` Richard Biener
2015-08-19 15:07 ` Michael Matz
2015-08-19 15:25 ` Richard Biener [this message]
2015-08-19 15:39 ` Richard Sandiford
-- strict thread matches above, loose matches on Subject: below --
2015-08-06 9:39 David Sherwood
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=D248FF31-2CB2-496B-A732-254ECF34A905@gmail.com \
--to=richard.guenther@gmail.com \
--cc=david.sherwood@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=richard.sandiford@arm.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).