public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Han-Kwang Nienhuys <h.nienhuys@amolf.nl>
To: gcc@gcc.gnu.org
Subject: Re: i386 rounding modes and workaround solution
Date: Tue, 11 Sep 2001 08:36:00 -0000	[thread overview]
Message-ID: <20010911173619.A7435@vd5.amolf.nl> (raw)
In-Reply-To: <006001c13a0c$b65fe140$7edd18ac@amr.corp.intel.com>

Oops, I think I barely missed the flamewar button...

I wasn't aware that my gcc version (included in a major GNU/Linux
distribution, v 2.96) lags a lot behind the development work. Next
time I will do my homework better ;-)

The reason I brought up the issue here was that I couldn't find
much useful information on the web.

On Mon, 10 Sep 2001, Tim Prince wrote:

> If you are familiar with current P4 models, you will be aware
> that using more than 2 values of the fldcw mask will degrade
> performance seriously.  Which processors do you consider as
> belonging to the x86 family?

The factor 4 was on a Pentium 3. I also tested it on an Athlon,
without exact timings, but it did have quite an impact as well.

I checked the manuals; you are correct that alternating between two
values of the FLDCW (as with f-i conversion) is no problem on a P4,
but (int) floor() might be. Thank you for the remark.

Han-Kwang Nienhuys

FOM Institute voor Atomic and Molecular Physics,
Amsterdam, The Netherlands


      parent reply	other threads:[~2001-09-11  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  7:48 Han-Kwang Nienhuys
2001-09-10  7:53 ` Jan Hubicka
2001-09-10  8:24 ` Tim Prince
2001-09-11  2:13   ` Jan Hubicka
2001-09-11  8:36   ` Han-Kwang Nienhuys [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=20010911173619.A7435@vd5.amolf.nl \
    --to=h.nienhuys@amolf.nl \
    --cc=gcc@gcc.gnu.org \
    /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).