Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com,
	Michael Snyder <msnyder@redhat.com>,
	mec@shout.net
Subject: Re: Problem with altivec.h? [was: Elena -- where is altivec.h?]
Date: Fri, 17 May 2002 17:59:00 -0000	[thread overview]
Message-ID: <15589.42793.76432.808421@localhost.redhat.com> (raw)
In-Reply-To: <20020517225008.GA4899@branoic.wv.cc.cmu.edu>

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


  reply	other threads:[~2002-05-18  0:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2002-05-17 13:19 ` Elena -- where is altivec.h? Daniel Berlin
2002-05-17 15:58 Problem with altivec.h? [was: Elena -- where is altivec.h?] Michael Elizabeth Chastain
2002-05-17 18:01 ` Elena Zannoni
2002-05-21 11:34   ` 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=15589.42793.76432.808421@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.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