This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: -msse producing sse2 instructions
Hello there, thanks for the quick response.
Whilst I see if I can track down a small test program (it only occurs in the
big unwieldy programs right now, as these things always seem to do) here's
some extra info:
I'm compiling currently
with -mfpmath=387 -msse -mcpu=pentium3 -march=pentium3 and gcc 3.1.1-4 from
the very latest experimental cygwin distribution.
One of the problems with tracking this down is my machine is an Athlon MP
and has no trouble with SSE2 instructions, however a client's machine is an
Athlon 4 and exhibits the problem. And of course we need the SSE builtins
for speed improvements. -_-;;
Regards
---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com
----- Original Message -----
From: "Andreas Jaeger" <aj@suse.de>
To: "Dylan Cuthbert" <dylan@q-games.com>
Cc: <gcc@gcc.gnu.org>; "Jan Hubicka" <jh@suse.cz>
Sent: Sunday, July 21, 2002 9:08 PM
Subject: Re: -msse producing sse2 instructions
> "Dylan Cuthbert" <dylan@q-games.com> writes:
>
> > Hi there,
> >
> > I'm having problems compiling with the -msse option and cygwin's latest
gcc
> > (v3.1.1), it seems to be producing SSE2 instructions which my Athlon 4
is
> > faithfully reporting as illegal instructions. The athlon 4 should
support
> > standard SSE but not SSE2 instructions.
> >
> > The current illegal instruction (one of a few others I've had but
forgotten
> > to record) is:
> >
> > cvttss2si 0xffffffd8(%ebp),%eax
> >
> > Removing the -msse option completely of course clears up the problem but
I
> > want to use the builtins and the 128 bit vector types available
with -msse.
> >
> > Is there any way as a temporary solution to disable sse code generation
but
> > still allow use of the builtins?
>
> Please file a complete bug report including a small test program that
> shows this behaviour,
>
> Andreas
> --
> Andreas Jaeger
> SuSE Labs aj@suse.de
> private aj@arthur.inka.de
> http://www.suse.de/~aj