This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: "SSE instruction set disabled?"
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: "R. Kelley Cook" <robert_k_cook at comerica dot com>
- Cc: Jan Hubicka <jh at suse dot cz>, Scott Robert Ladd <scott at coyotegulch dot com>, <gcc at gcc dot gnu dot org>
- Date: Wed, 4 Dec 2002 19:21:04 +0000 (GMT)
- Subject: Re: "SSE instruction set disabled?"
On Wed, 4 Dec 2002, R. Kelley Cook wrote:
> This makes absolute complete sense.
>
> "-mmmx", "-msse", "-msse2", and "-m3dnow" (and their coresponding
> -mno-xxx) should just go away.
>
> They already are implied by -march=blahblah that we have. If someone
> wants code tuned for a pentium4, but without any SSE or MMX support then
> they can type "-march=pentiumpro -mcpu=pentium4"
Don't some CPU types exist in versions with and without some of these
features, or should this be allowed for by more fine-grained -march?
There's also the question of allowing people to specify the options that
are the closest approximation to right if they have some clone CPU that
doesn't have a specific GCC option.
> Although, in my opinion "-mcpu=" should be renamed "-mtune=" like was
> debated ages ago: http://gcc.gnu.org/ml/gcc/1999-01n/msg01004.html
I think the last proposal was for consistently named --arch / --tune
options across all targets (with corresponding ability for --help to list
the supported types with descriptions) ("gcc/config/mips/mips.h reorg"
thread on gcc-patches, June 2001).
--
Joseph S. Myers
jsm28@cam.ac.uk