Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Stephen Holford <sholford@WESCAM.com>
Cc: gdb@sources.redhat.com
Subject: Re: PowerPC UISA registers and altivec
Date: Fri, 31 May 2002 08:20:00 -0000	[thread overview]
Message-ID: <15607.38035.350353.557111@localhost.redhat.com> (raw)
In-Reply-To: <001b01c208b2$40a12a20$d158010a@burlington.wescam.com>

Stephen Holford writes:
 > Hi
 > 
 > In GDB release 5.2 the powerpc altivec registers have appeared as part of
 > the register set used by the default architecture powerpc:common. These
 > registers now appear in "info reg" commands, or in the register list from
 > the insight GUI. Does it make sense to require the altivec registers to be
 > part of powerpc:common? Most powerpc's don't have these registers (my
 > viewpoint is from the embedded 8xx, 82xx world).
 > 
 > Steve
 > ----------------------------------------------------------------
 > Stephen F. Holford, P.Eng.
 > Wescam
 > (905) 633-4000 x2119

I agree with you that this is a quite unfortunate situation. It would
be nice if the bfd contained some indication of the particular
architecture in use, so that gdb could automatically switch to 7400
and only then display these registers. 

For your case, could you do a 'set architecture powerpc:8xx' in gdb?
That will give you the exact register set for your platform.


See the (long) thread at:
http://sources.redhat.com/ml/gdb-patches/2001-11/msg00548.html


Elena


      reply	other threads:[~2002-05-31 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  7:40 Stephen Holford
2002-05-31  8:20 ` Elena Zannoni [this message]

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=15607.38035.350353.557111@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=sholford@WESCAM.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