This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/34038] 176.gcc segfaults when compiled with -O2 -ftree-vectorize -maltivec
- From: "janis at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Dec 2007 23:34:54 -0000
- Subject: [Bug tree-optimization/34038] 176.gcc segfaults when compiled with -O2 -ftree-vectorize -maltivec
- References: <bug-34038-4503@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from janis at gcc dot gnu dot org 2007-12-12 23:34 -------
Ira, it seems I've wasted your time; it's a well-known problem (except to me)
that -maltivec without -mabi=altivec doesn't work in the general case because
vector registers are not saved and restored. That explains why this test
passes with either reload.c or reload1.c is compiled without vectorization.
Meanwhile there are discussions happening about how to fix this so that someone
using "-O3 -mcpu=970" won't run into failures when they don't even realize
they're using vector registers.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34038