From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-15790-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 31332 invoked by alias); 21 May 2002 16:23:30 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 31308 invoked from network); 21 May 2002 16:23:28 -0000
Received: from unknown (HELO cygnus.com) (205.180.83.203)
  by sources.redhat.com with SMTP; 21 May 2002 16:23:28 -0000
Received: from localhost.redhat.com (remus.sfbay.redhat.com [172.16.27.252])
	by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id JAA03031;
	Tue, 21 May 2002 09:23:14 -0700 (PDT)
Received: by localhost.redhat.com (Postfix, from userid 469)
	id E4FEA10FC9; Tue, 21 May 2002 12:22:37 -0400 (EDT)
From: Elena Zannoni <ezannoni@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15594.29773.463633.959139@localhost.redhat.com>
Date: Tue, 21 May 2002 11:34:00 -0000
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>, gdb-patches@sources.redhat.com,
        msnyder@redhat.com
Subject: Re: Problem with altivec.h? [was: Elena -- where is altivec.h?]
In-Reply-To: <15589.42934.379243.211740@localhost.redhat.com>
References: <200205172258.g4HMwfJ19933@duracef.shout.net>
	<15589.42934.379243.211740@localhost.redhat.com>
X-SW-Source: 2002-05/txt/msg00838.txt.bz2

Elena Zannoni writes:
 >  > Suggestion:
 >  > 
 >  > I did a find in the gcc source:
 >  > 
 >  >   % find * -name '*altivec*' -print
 >  >   gcc/config/rs6000/altivec.h
 >  >   gcc/config/rs6000/altivec-defs.h
 >  >   gcc/config/rs6000/eabialtivec.h
 >  >   gcc/config/rs6000/linuxaltivec.h
 >  >   gcc/testsuite/gcc.dg/altivec-1.c
 >  >   gcc/testsuite/gcc.dg/altivec-2.c
 >  >   gcc/testsuite/gcc.dg/altivec-3.c
 >  >   gcc/testsuite/gcc.dg/altivec-4.c
 >  >   gcc/testsuite/gcc.dg/altivec-5.c
 >  >   gcc/testsuite/gcc.dg/altivec-7.c
 >  >   gcc/testsuite/gcc.dg/altivec-8.c
 >  > 
 >  > Most of the altivec-*.c test files do not use altivec.h.  They simply
 >  > use builtin keywords directly.  Have a look at altivec-4.c. 
 >  > You could write the tests like that.
 >  > 
 > 
 > Yes, actually I asked Aldy and that is what he suggested doing, just put the
 > necessary #define (just one) in the .c files. I'll do that.
 > 

I get compilation errors, if I don't include the full altivec.h,
I'll leave it as it is now.

Elena