From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH-ppc 2/5] Add VSX support for core-files
Date: Thu, 14 Aug 2008 19:52:00 -0000 [thread overview]
Message-ID: <200808141951.m7EJpjWM025421@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <1217016947.29012.76.camel@gargoyle> from "Luis Machado" at Jul 25, 2008 05:15:46 PM
Luis Machado wrote:
> 2008-07-25 Luis Machado <luisgpm@br.ibm.com>
>
> * ppc-linux-tdep.c (ppc_linux_regset_sections): Add new ".reg-ppc-vsx" field.
> (ppc32_linux_vsxregset): New 32-bit VSX-enabled regset.
> (ppc_linux_regset_from_core_section): Handle VSX core section.
> (ppc_linux_core_read_description): Support VSX-enabled core files.
>
> * corelow.c (get_core_register_section): Support VSX-enabled
> core files.
This is OK.
> Index: gdb/corelow.c
> ===================================================================
> --- gdb.orig/corelow.c 2008-07-23 09:28:09.000000000 -0700
> +++ gdb/corelow.c 2008-07-23 09:31:44.000000000 -0700
> @@ -499,6 +499,8 @@
> ".reg-xfp", 3, "extended floating-point", 0);
> get_core_register_section (regcache,
> ".reg-ppc-vmx", 3, "ppc Altivec", 0);
> + get_core_register_section (regcache,
> + ".reg-ppc-vsx", 4, "POWER7 VSX", 0);
It would be nice if we could convert this to a loop using the
gdbarch_core_regset_sections list at some point ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-08-14 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 20:16 Luis Machado
2008-08-08 15:18 ` Luis Machado
2008-08-21 19:53 ` Ulrich Weigand
2008-08-21 21:10 ` Luis Machado
2008-08-21 21:14 ` Ulrich Weigand
2008-08-22 22:32 ` Luis Machado
2008-08-25 18:27 ` Ulrich Weigand
2008-08-26 15:32 ` Luis Machado
2008-08-14 19:52 ` Ulrich Weigand [this message]
2008-08-15 5:14 ` Luis Machado
2008-08-15 15:27 ` 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=200808141951.m7EJpjWM025421@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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