--- Comment #8 from janis at gcc dot gnu dot org 2009-07-08 19:48 ---
Fixed awhile ago by changing -mabi=altivec to the default for powerpc*-linux.
--
janis at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #7 from janis at gcc dot gnu dot org 2007-12-12 23:28 ---
I had assumed that -maltivec -mabi=no-altivec was supposed to work in the
general case, then had some discussions about it on #gcc today and learned that
it doesn't and is a known problem. Given that, we ought to add
--- Comment #6 from jakub at gcc dot gnu dot org 2007-12-12 17:51 ---
As -m32 -maltivec without -mabi=altivec has the VMX regs effectively neither
fixed, nor call saved, nor call used, it simply can't work reliably.
Registers really need to have some rules for using them, while -m32 -mal
--- Comment #5 from janis at gcc dot gnu dot org 2007-12-12 17:44 ---
It's legitimate to use -maltivec without -mabi=altivec unless linking against
objects that were compiled with -mabi=altivec, so adding the option to vect.exp
is merely hiding the problem. Is there a reason why only th
--- Comment #4 from janis at gcc dot gnu dot org 2007-12-11 23:27 ---
The patch in comment #3 works, except that there need to be quotes around each
option: "-maltivec" "-mabi=altivec".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34437
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-12-11 23:08 ---
Or someone messed up vect.exp :(.
Anyways try this patch:
Index: testsuite/gcc.dg/vect/vect.exp
===
--- testsuite/gcc.dg/vect/vect.exp (revision 1
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-12-11 23:05 ---
No the autovectorizer testsuite uses -mabi=altivec also.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34437
--- Comment #1 from jakub at gcc dot gnu dot org 2007-12-11 23:00 ---
See http://gcc.gnu.org/ml/gcc-patches/2007-11/msg00340.html
Apparently -m32 -maltivec has been always badly broken.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34437
