From: Andreas Jaeger <aj@suse.de>
To: Casey Leedom <casey_leedom@yahoo.com>
Cc: Jan Hubicka <jh@suse.cz>, Joe Buck <jbuck@synopsys.com>,
dann@godzilla.ics.uci.edu, mark@codesourcery.com,
gcc@gcc.gnu.org, dan@dberlin.org
Subject: Re: SPEC2000 252.eon generates invalid results when compiled -O3 with g++ 3.3
Date: Sat, 29 Mar 2003 09:49:00 -0000 [thread overview]
Message-ID: <u88yuywy2m.fsf@gromit.moeb> (raw)
In-Reply-To: <20030328214304.47039.qmail@web13104.mail.yahoo.com> (Casey Leedom's message of "Fri, 28 Mar 2003 13:43:04 -0800 (PST)")
Casey Leedom <casey_leedom@yahoo.com> writes:
> / Date: Fri, 28 Mar 2003 02:21:56 +0100
> | From:"Jan Hubicka" <jh@suse.cz>
> |
> | > Okay, adding -fpmath=sse solved the problem. Interestingly enough adding
> | > "-march=k8 -mcpu=k8" wasn't good enough. I would have thought that it
> | > would have been from reading gcc/config/i386/i386.c:override_options() ...
> |
> | We've been chatting about this with glibc folks and they don't like the
> | idea of losing the extra precisity 80bit temrporaries give, so
> \ -mfpmath=sse can't be the default, unforutnately :(
>
> Okay, I understand that. So let me see if I'm 100% on the same page (I'm
> very new to the x86 instruction set and it's history):
>
> 1. x87 is a stack-based floating point co-processor (originally on a separate
> chip). It performs calulations in 80-bit arithmetic for "double"s?
>
> 2. SSE is a register-file floating point engine. It was designed to support
> digital media applications and performs 64-bit arithmetic for "doubles"?
>
> 3. SSE2 is an update of SSE that extends the arithmetic to use 128-bit
> (80-bit?) arithmetic for "doubles"?
SSE and SSE2 together (don't remember what introduced what) have:
- 32-bit floats and performs 32-bit float arithmetic for these
- 64-bit doubles and performs 64-bit double arithmetic for these
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2003-03-29 5:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 23:21 Casey Leedom
2003-03-27 23:47 ` Joe Buck
2003-03-27 23:49 ` Casey Leedom
2003-03-28 0:04 ` Jan Hubicka
2003-03-28 0:19 ` Casey Leedom
2003-03-28 4:21 ` Casey Leedom
2003-03-28 7:49 ` Jan Hubicka
2003-03-28 23:57 ` Casey Leedom
2003-03-29 5:19 ` Jan Hubicka
2003-03-29 8:27 ` Jan Hubicka
2003-03-29 9:49 ` Andreas Jaeger [this message]
2003-03-28 0:58 ` Vladimir Makarov
2003-03-28 11:58 ` Jan Hubicka
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=u88yuywy2m.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=casey_leedom@yahoo.com \
--cc=dan@dberlin.org \
--cc=dann@godzilla.ics.uci.edu \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=jh@suse.cz \
--cc=mark@codesourcery.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).