From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>,
"Reynolds,
Terry (Contractor-SIMTECH)" <terry.reynolds2@us.army.mil>
Subject: Re: ppc64 altivec registers?
Date: Wed, 07 Sep 2005 19:06:00 -0000 [thread overview]
Message-ID: <200509071206.15086.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050907133001.GA3921@nevyn.them.org>
On Wednesday 07 September 2005 06:30, Daniel Jacobowitz wrote:
> On Wed, Sep 07, 2005 at 08:26:57AM -0500, Reynolds, Terry (Contractor-SIMTECH) wrote:
> > Hi,
> >
> > Does anyone here know how to fix the configuration of the kernel so that
> > gdb can find the altivec registers? The last time I heard from Andrew
> > Cagney he said :
> >
> > "At the time the code was written it was for a special altivec kernel /
> > build / config. Hence it was only enabled when built powerpc-*-*altivec.
> > Time has passed and that restriction no longer applies. I'll see about
> > removing it."
>
> Probably, the clean way to do this is through the "optional register
> set" interface we defined a couple of months ago. But I haven't had
> time to implement that yet.
>
(One of) The problem(s) with Altivec is with the kernel and not with GDB. The kernel (not sure which version, but I think all) just left out the GETVRREGS
and PUTVRREGS parts of the ptrace system call. Even with a patched kernel, there seems to be some problems with Altivec. I am working on them. I
hope to turn all the 'FAILS' to 'PASSES' in the the Altivec part of the testsuite (gdb.arch/altivec-abi.exp and gdb.arch/altivec-regs.exp)
Here is a link to a experimental patch to the 64-bit kernel that seems to fix the ptrace part of the problem(s):
http://ozlabs.org/pipermail/linuxppc64-dev/2005-August/005269.html
prev parent reply other threads:[~2005-09-07 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 13:27 Reynolds, Terry (Contractor-SIMTECH)
2005-09-07 13:30 ` Daniel Jacobowitz
2005-09-07 19:06 ` Paul Gilliam [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=200509071206.15086.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=terry.reynolds2@us.army.mil \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).