From: Elena Zannoni <ezannoni@redhat.com>
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?]
Date: Tue, 21 May 2002 11:34:00 -0000 [thread overview]
Message-ID: <15594.29773.463633.959139@localhost.redhat.com> (raw)
In-Reply-To: <15589.42934.379243.211740@localhost.redhat.com>
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
next prev parent reply other threads:[~2002-05-21 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 15:58 Michael Elizabeth Chastain
2002-05-17 18:01 ` Elena Zannoni
2002-05-21 11:34 ` Elena Zannoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 13:08 Elena -- where is altivec.h? Michael Snyder
2002-05-17 13:12 ` Elena Zannoni
2002-05-17 15:40 ` Problem with altivec.h? [was: Elena -- where is altivec.h?] Elena Zannoni
2002-05-17 15:50 ` Daniel Jacobowitz
2002-05-17 17:59 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15594.29773.463633.959139@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=msnyder@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox