From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-101577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 18208 invoked by alias); 30 Jun 2004 00:15:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 18199 invoked by uid 48); 30 Jun 2004 00:15:12 -0000
Date: Wed, 30 Jun 2004 00:30:00 -0000
From: "paulus at samba dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20040630001511.16286.paulus@samba.org>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug c/16286] New: Compile errors on altivec ops after #undef vector
X-Bugzilla-Reason: CC
X-SW-Source: 2004-06/txt/msg03869.txt.bz2
List-Id: <gcc-bugs.sourceware.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