This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with altivec.h? [was: Elena -- where is altivec.h?]


Daniel Jacobowitz writes:
 > On Fri, May 17, 2002 at 06:39:30PM -0400, Elena Zannoni wrote:
 > > Elena Zannoni writes:
 > >  > Michael Snyder writes:
 > >  >  > Hi, 
 > >  >  > 
 > >  >  > gdb.arch refers to this file, but I can't find it.
 > >  >  > 
 > >  >  > Michael
 > >  > 
 > >  > It's in gcc/config/rs6000 I think. If not it's somewhere close to that.
 > >  > It's in gcc definitely.
 > >  > 
 > >  > Elena
 > > 
 > > MichaelS reminded me (private e-mail) that we cannot have gcc files
 > > being required by the gdb tree. 
 > > I guess we should make our own copy of altivec.h?
 > 
 > I don't think that's quite right.  <altivec.h> is an _installed_ gcc
 > file.  It goes into gcc-lib/.../include.
 > 
 > If the file is not found, we shouldn't be running the tests.
 > 

That was my thought originally. Unless there is a gcc with the right
bits the tests won't work anyway. But I thought I was missing
something in the bigger picture.

Elena


 > > 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.
 > > 
 > > I could just add a copy to the gdb.arch directory. or include/gdb ?
 > > What's the procedure here?
 > > 
 > > 
 > > Elena
 > 
 > -- 
 > Daniel Jacobowitz                           Carnegie Mellon University
 > MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]