> If no --with-cpu is specified at configure time gcc/config.gcc sets the
> "cpu" option in configure_default_options to `v9' in sparc64 targets.
> This leads to the usage of the following spec by the driver:
>
> %{!m32:%{!mcpu=*:-mcpu=v9}}
>
> Which in turn triggers the usage of -Av9 by default when invoking the
> assembler. This leads to failures when VIS instructions are used in
> inline assembly or .s files:
>
> [jemarch@install2 gcc]$ echo 'int main () { asm ("fzero %f0"); return 0; }'
> | gcc -xc - /tmp/cc1F9iJm.s: Assembler messages:
> /tmp/cc1F9iJm.s:11: Error: Architecture mismatch on "fzero".
> /tmp/cc1F9iJm.s:11: (Requires v9a|v9b; requested architecture is v9.)
I think that passing -mcpu=ultrasparc -mvis is a reasonable expectation when
VIS instructions are used.
> This prevents building upstream glibc with a gcc configured with not
> --with-cpu option, for example.
Certainly annoying.
> I think it would be reasonable to have gcc targetting ultrasparc
> extensions by default in sparc64-*-linux*. WDYT?
No strong opinion. FreeBSD and OpenBSD already do it so why not?
DaveM, any opinion?
--
Eric Botcazou
