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: Uros Bizjak <uros dot bizjak at kss-loka dot si>
To: Evan Cheng <echeng at apple dot com>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 04 Oct 2005 10:07:07 +0200
Subject: Re: Should -msse3 enable fisttp?
References: <179A6816-4A60-4FC6-B9AE-CC920FBBC16A@apple.com> <E7B54782-15C9-494F-BBFF-8E05DAFF317C@apple.com> <1128409563.434229db8eba2@ssl.kss-loka.si>
Reply-to: ubizjak at gmail dot com

Quoting Uros Bizjak <uros@kss-loka.si>:

>   Following simple patch should implement your suggested approach:
> 
> -march=prescott           enables fisttp
> -msse3                    enables fisttp
> -march=prescott -mno-sse3 enables fisttp
> 
> Otherwise fisttp is disabled.

This one also works for -mno-80387 and simplifies insn pattern constraints a bit:

2005-10-05  Uros Bizjak  <uros@kss-loka.si>

	* config/i386/i386.h (TARGET_FISTTP): Enable also for
	TARGET_SSE3 and only for TARGET_80387.
	* config/i386/i386.md (fix_trunc<mode>_fisttp_i387_1,
	(fix_trunc<mode>_i387_fisttp, fix_trunc<mode>_i387_fisttp_with_temp):
	Do not depend on TARGET_80387.

Uros.

Attachment: fisttp_2.diff
Description: Binary data

Follow-Ups:
- Re: Should -msse3 enable fisttp?
  - From: Paolo Bonzini
- Re: Should -msse3 enable fisttp?
  - From: Richard Henderson

References:
- Re: Should -msse3 enable fisttp?
  - From: Evan Cheng
- Re: Should -msse3 enable fisttp?
  - From: Uros Bizjak

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