public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Michael Sturm <michael.sturm@intel.com>
To: palves@redhat.com, eliz@gnu.org, mark.kettenis@xs4all.nl,
	       walfred.tedeschi@intel.com
Cc: gdb-patches@sourceware.org, Michael Sturm <michael.sturm@intel.com>
Subject: [PATCH v1 3/3] Add AVX512 feature description to GDB manual
Date: Fri, 20 Dec 2013 09:53:00 -0000	[thread overview]
Message-ID: <1387533175-4039-4-git-send-email-michael.sturm@intel.com> (raw)
In-Reply-To: <1387533175-4039-1-git-send-email-michael.sturm@intel.com>

2013-09-11  Michael Sturm  <michael.sturm@intel.com>
            Walfred Tedeschi  <walfred.tedeschi@intel.com>

     * NEWS: Add note about new support for AVX512.
doc/
     * gdb.texinfo (i386 Features): Add description of AVX512
     registers.

---
 gdb/NEWS            |  5 +++++
 gdb/doc/gdb.texinfo | 34 ++++++++++++++++++++++++++++++++++
 2 files changed, 39 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index ae84e00..ed4349a 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -5579,3 +5579,8 @@ Host is the machine where GDB will run; targ is the machine
 where the program that you are debugging will run.
 
  *  GDB now supports access to Intel(R) MPX registers on GNU/Linux.
+
+ *  Support for Intel(R) AVX-512 registers on GNU/Linux.
+
+Support displaying and modifying Intel(R) AVX-512 registers $zmm0 - $zmm31 and
+$k0 - $k7 on GNU/Linux.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 87d5145..ed8ee32 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -43287,6 +43287,40 @@ Memory Protection Extension (MPX).  It should describe the following registers:
 The @samp{org.gnu.gdb.i386.linux} feature is optional.  It should
 describe a single register, @samp{orig_eax}.
 
+The @samp{org.gnu.gdb.i386.avx512} feature is optional and requires the
+@samp{org.gnu.gdb.i386.avx} feature.  It should
+describe additional @sc{xmm} registers:
+
+@itemize @minus
+@item
+@samp{xmm16h} through @samp{xmm31h} for amd64
+@end itemize
+
+It should describe the upper 128 bits of additional @sc{ymm} registers:
+
+@itemize @minus
+@item
+@samp{ymm16h} through @samp{ymm31h} for amd64
+@end itemize
+
+It should
+describe the upper 256 bits of @sc{zmm} registers:
+
+@itemize @minus
+@item
+@samp{zmm0h} through @samp{zmm7h} for i386
+@item
+@samp{zmm0h} through @samp{zmm15h} for amd64
+@end itemize
+
+It should
+describe the additional @sc{zmm} registers:
+
+@itemize @minus
+@item
+@samp{zmm16h} through @samp{zmm31h} for amd64
+@end itemize
+
 @node MIPS Features
 @subsection @acronym{MIPS} Features
 @cindex target descriptions, @acronym{MIPS} features
-- 
1.8.4.2

  reply	other threads:[~2013-12-20  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  9:53 [PATCH v1 0/3] Intel(R) AVX-512 register support Michael Sturm
2013-12-20  9:53 ` Michael Sturm [this message]
2013-12-20 10:39   ` [PATCH v1 3/3] Add AVX512 feature description to GDB manual Eli Zaretskii
2013-12-20  9:53 ` [PATCH v1 1/3] Add AVX512 registers support to GDB Michael Sturm
2013-12-20 17:29   ` Pedro Alves
2014-01-14  9:01     ` Sturm, Michael
2013-12-20  9:53 ` [PATCH v1 2/3] Add AVX512 register support to gdbserver Michael Sturm

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=1387533175-4039-4-git-send-email-michael.sturm@intel.com \
    --to=michael.sturm@intel.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=palves@redhat.com \
    --cc=walfred.tedeschi@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).