This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Should -msse3 enable fisttp
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Evan Cheng <evan dot cheng at apple dot com>
- Cc: Evan Cheng <echeng at apple dot com>, gcc at gcc dot gnu dot org
- Date: Mon, 3 Oct 2005 18:25:28 -0400
- Subject: Re: Should -msse3 enable fisttp
- References: <179A6816-4A60-4FC6-B9AE-CC920FBBC16A@apple.com> <9C9C4DF4-8B8D-411F-920C-92A4C385633F@apple.com>
On Oct 3, 2005, at 5:56 PM, Evan Cheng wrote:
My mistake. I misunderstood the meaning of -msse3 (it only enables the
sse3 builtins). Please ignore.
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.
Hmm, but from the original patch:
http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01119.html
"BTW: Regarding TARGET_FISTTP macro: according to documentation, fisttp
insn indeed depends on (TARGET_80387 && TARGET_SSE3). However, this
insn is not a SSE3 instruction, so it should not be disabled by
-mno-sse3 flag."
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.
Thanks,
Andrew Pinski