--
jsm28 at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37349
--- You are
> v9 means 64 bits. You probably want to use v8plus instead, which
> corresponds to 32-bit instructions on an UltraSparc CPU.
Not necessarily. If you pass -mcpu=v9 to the 32-bit SPARC compiler, it still
emits code which is compliant with the 32-bit ABI.
On Solaris the 32-bit compiler defaults t
Matthias Klose a écrit :
> I'm currently building trunk on sparc-linux-gnu (32bit) configured with
>
> --enable-targets=all --with-cpu=v8
>
> trying to change that to
>
> --enable-targets=all --with-cpu=v9
>
> two 64bit libgcc's are built. it looks like v9 and 64bit are tightly
> coupled in
I'm currently building trunk on sparc-linux-gnu (32bit) configured with
--enable-targets=all --with-cpu=v8
trying to change that to
--enable-targets=all --with-cpu=v9
two 64bit libgcc's are built. it looks like v9 and 64bit are tightly
coupled in the configury. how can this be setup to buil
I'm currently building trunk on sparc-linux-gnu (32bit) configured with
--enable-targets=all --with-cpu=v8
trying to change that to
--enable-targets=all --with-cpu=v9
two 64bit libgcc's are built. it looks like v9 and 64bit are tightly
coupled in the configury. how can this be setup to buil
5 matches
Mail list logo