Elena -- where is altivec.h?

Elena -- where is altivec.h?

[Michael Snyder]

Hi, 

gdb.arch refers to this file, but I can't find it.

Michael

Re: Elena -- where is altivec.h?

[Elena Zannoni]

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

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

[Elena Zannoni]

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?

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

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

[Daniel Jacobowitz]

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.

> 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

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

[Elena Zannoni]

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

Re: Elena -- where is altivec.h?

[Daniel Berlin]

On Fri, 17 May 2002, Michael Snyder wrote:

> Hi, 
> 
> gdb.arch refers to this file, but I can't find it.
It's installed by gcc.

> 
> Michael
> 

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

[Michael Elizabeth Chastain]

> 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

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

[Elena Zannoni]

Michael Elizabeth Chastain writes:
 > > 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.
 > 

Yes, true. Long day, sorry.

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

Yes, that's what happens.

 > 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).
 > 

No, I have found no problems with the tests. I was trying to address
MichaelS concerns.

 > 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.

Elena


 > Michael C

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

[Elena Zannoni]

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