This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Should -msse3 enable fisttp

From: Eric Christopher <echristo at apple dot com>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Evan Cheng <evan dot cheng at apple dot com>, Evan Cheng <echeng at apple dot com>, gcc at gcc dot gnu dot org
Date: Mon, 3 Oct 2005 15:46:35 -0700
Subject: Re: Should -msse3 enable fisttp
References: <179A6816-4A60-4FC6-B9AE-CC920FBBC16A@apple.com> <9C9C4DF4-8B8D-411F-920C-92A4C385633F@apple.com> <96c4c14efd48ceaf2e289ccfdd3c34bb@physics.uc.edu>

Actually it enables more than the builtins. It enables the use sse3 instructions. This is just like -maltivec on PowerPC and -msse and -msse on x86, etc.

Right, so the manual disagrees and should probably be fixed.

And then RTH agreed:
http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01432.html
So from the sound of it fisttp is not a SSE3 instruction.

Richard's response was that it shouldn't be turned off by -mno-sse3, not that it shouldn't be turned on for -msse3. I think it probably should be turned on there.

-eric

References:
- Re: Should -msse3 enable fisttp
  - From: Evan Cheng
- Re: Should -msse3 enable fisttp
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]