From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH-ppc 5/5] Add VSX doc bits
Date: Fri, 25 Jul 2008 20:16:00 -0000 [thread overview]
Message-ID: <1217016956.29012.79.camel@gargoyle> (raw)
Last, but not the least, this adds some documentation about the new
register set. It's not very descriptive, but as the patches may change a
bit, i'll leave this one to the end. It'll probably require a NEWS entry
as well.
---
2008-07-25 Luis Machado <luisgpm@br.ibm.com>
* doc/gdb.texinfo: Updated documentation with new support info.
Index: gdb/doc/gdb.texinfo
===================================================================
--- gdb.orig/doc/gdb.texinfo 2008-07-23 09:28:06.000000000 -0700
+++ gdb/doc/gdb.texinfo 2008-07-23 09:31:44.000000000 -0700
@@ -16210,6 +16210,9 @@
by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0},
@code{f2} and @code{f3} for @code{$dl1} and so on.
+For POWER7 processors, GDB provides a new set of pseudo-registers, the 64-bit
+wide Extended Floating Point Registers (@samp{f32} through @samp{f63}).
+
@node Controlling GDB
@chapter Controlling @value{GDBN}
@@ -27406,6 +27409,13 @@
contain registers @samp{vr0} through @samp{vr31}, @samp{vscr},
and @samp{vrsave}.
+The @samp{org.gnu.gdb.power.vsx} feature is optional. It should
+contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN}
+will combine these registers with the floating point registers
+(@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0}
+through @samp{vr31}} to present the 128-bit wide registers @samp{vs0}
+through @samp{vs63}, the new set of vector registers for POWER7.
+
The @samp{org.gnu.gdb.power.spe} feature is optional. It should
contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and
@samp{spefscr}. SPE targets should provide 32-bit registers in
next reply other threads:[~2008-07-25 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 20:16 Luis Machado [this message]
2008-08-15 15:29 ` Luis Machado
2008-08-15 15:39 ` Stan Shebs
2008-08-15 15:52 ` Luis Machado
2008-08-15 17:08 ` Eli Zaretskii
2008-08-15 18:14 ` Luis Machado
2008-08-15 18:22 ` Eli Zaretskii
2008-08-18 16:02 ` Luis Machado
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=1217016956.29012.79.camel@gargoyle \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/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