This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Problem with altivec.h? [was: Elena -- where is altivec.h?]
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