Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yufeng Zhang <Yufeng.Zhang@arm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: [PATCH, AArch64] Update the gregset size
Date: Fri, 08 Feb 2013 11:51:00 -0000	[thread overview]
Message-ID: <5114E6CD.5010102@arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

Hi,

Following the recent bug fix in the AArch64 kernel, this patch updates 
the expected size of the general register set in core dump file.

OK to commit?

Thanks,
Yufeng

gdb/

2013-02-08  Yufeng Zhang  <yufeng.zhang@arm.com>

	* aarch64-linux-tdep.c (AARCH64_LINUX_SIZEOF_GREGSET): Change the
	number of the registers from 36 to 34.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: aarch64-correct-gregset-size-gdb.patch --]
[-- Type: text/x-patch; name=aarch64-correct-gregset-size-gdb.patch, Size: 750 bytes --]

diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index 3055a0a..8e66425 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -36,9 +36,9 @@
 #include "regset.h"
 
 /* The general-purpose regset consists of 31 X registers, plus SP, PC,
-   PSTATE and two extra pseudo 64-bit registers, as defined in the
-   AArch64 port of the Linux kernel.  */
-#define AARCH64_LINUX_SIZEOF_GREGSET  (36 * X_REGISTER_SIZE)
+   and PSTATE registers, as defined in the AArch64 port of the Linux
+   kernel.  */
+#define AARCH64_LINUX_SIZEOF_GREGSET  (34 * X_REGISTER_SIZE)
 
 /* The fp regset consists of 32 V registers, plus FPCR and FPSR which
    are 4 bytes wide each, and the whole structure is padded to 128 bit

             reply	other threads:[~2013-02-08 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 11:51 Yufeng Zhang [this message]
2013-02-08 12:16 ` Pedro Alves

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=5114E6CD.5010102@arm.com \
    --to=yufeng.zhang@arm.com \
    --cc=Marcus.Shawcroft@arm.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