From: Tim Prince <tprince@myrealbox.com>
To: Petr Savicky <savicky@cs.cas.cz>
Cc: Nick Maclaren <nmm1@cus.cam.ac.uk>, gcc-help@gcc.gnu.org
Subject: Re: where to discuss problems with IEEE 754 standard on x86 architecture?
Date: Wed, 23 May 2007 13:30:00 -0000 [thread overview]
Message-ID: <4654395D.307@myrealbox.com> (raw)
In-Reply-To: <20070523070851.GA2951@cs.cas.cz>
Petr Savicky wrote:
>> You were using -mfpmath=387 (possible as the default), and that uses
>> Intel native arithmetic, which is NOT standard IEEE 754 double, but
>> an extended format.
>>
>> If you use -mfpmath=sse, you will get what you expect.
>>
>>
> Thank you for your reply. This explains the problem.
>
> However, solving the problem seems to be harder.
> I tried "gcc -mfpmath=sse", but obtained the warning:
> SSE instruction set disabled, using 387 arithmetics.
>
> gcc version: 3.3.3
> uname -m -p -i: i686 i686 i386
> /proc/cpuinfo:
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Xeon(TM) CPU 2.80GHz
>
> I obtained the same on another computer with
> gcc version: 4.1.0
> uname -m -p -i: i686 i686 i386
> /proc/cpuinfo:
> vendor_id : GenuineIntel
> cpu family : 6
> model : 8
> model name : Celeron (Coppermine)
>
> man gcc says: For the i386 compiler, you need to use -march=cpu-type, -msse or -msse2 switches
> to enable SSE extensions and make this option effective.
> The choices for cpu-type are the same as for -mtune.
> -mtune=cpu-type has possible values itanium, itanium1, merced, itanium2, and mckinley
> none of which seems to fit my computers.
>
> With "gcc -mfpmath=sse -msse" I obtained no warning/error, but the program
> behaves in the old wrong way.
>
> So, I think that SSE is not available on my computers. Is this correct?
>
>
Why didn't you follow the advice you quoted?
gcc -march=pentium4 -mfpmath=sse
When you compile code for pentium2, of course SSE is not available to
the compiler.
next prev parent reply other threads:[~2007-05-23 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 20:41 Nick Maclaren
2007-05-23 7:44 ` Petr Savicky
2007-05-23 8:17 ` Nick Maclaren
2007-05-23 8:46 ` Brian Dessent
2007-05-23 13:30 ` Tim Prince [this message]
2007-05-23 17:23 ` Petr Savicky
-- strict thread matches above, loose matches on Subject: below --
2007-05-22 20:25 Nick Maclaren
2007-05-22 20:05 Petr Savicky
2007-05-22 20:06 ` John (Eljay) Love-Jensen
2007-05-23 12:54 ` Andrew Haley
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=4654395D.307@myrealbox.com \
--to=tprince@myrealbox.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nmm1@cus.cam.ac.uk \
--cc=savicky@cs.cas.cz \
--cc=tprince@computer.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).