This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/16286] New: Compile errors on altivec ops after #undef vector
- From: "paulus at samba dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Jun 2004 00:15:12 -0000
- Subject: [Bug c/16286] New: Compile errors on altivec ops after #undef vector
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
The Altivec PIM says that programs may #undef vector and/or pixel if desired.
However, doing that with the current <altivec.h> leads to compile errors.
This test program:
#include <altivec.h>
#undef vector
void test(void)
{
__vector unsigned int a, b;
a = vec_and(a, b);
}
gives the error:
vb2.c: In function `test':
vb2.c:8: error: parse error before "vector"
when compiled with gcc -c -maltivec. If I take out the #undef vector then
the error doesn't occur.
--
Summary: Compile errors on altivec ops after #undef vector
Product: gcc
Version: 3.3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: paulus at samba dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: powerpc-linux
GCC host triplet: powerpc-linux
GCC target triplet: powerpc-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16286