From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-15719-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 13572 invoked by alias); 17 May 2002 22:58:44 -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 13562 invoked from network); 17 May 2002 22:58:43 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by sources.redhat.com with SMTP; 17 May 2002 22:58:43 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id g4HMwfJ19933;
	Fri, 17 May 2002 17:58:41 -0500
Date: Fri, 17 May 2002 15:58:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200205172258.g4HMwfJ19933@duracef.shout.net>
To: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Problem with altivec.h? [was: Elena -- where is altivec.h?]
Cc: msnyder@redhat.com
X-SW-Source: 2002-05/txt/msg00767.txt.bz2

> In case this is not obvious, the altivec C testsfiles (or any altivec
> programs) need to include this <altivec.h> gcc file because it has
> all the necessary #defines for vector types.

include/gdb is for building gcc and gdb, not for building target
programs.  Consider a cross-compiler + cross-debugger + simulator:
host=i686-pc-linux-gnu, target=rs6000-unknown-whatever.  So that
directory is right out.

gcc should be installing altivec.h with the other target include files.
AldyH would know about that.

Perhaps you are testing out of a build directory, rather than an install
directory, and the dejagnu machinery is not producing enough -I flags?
(I am studying this area right now because I'm working on Petr's
f77/f95 patch).

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.

Michael C