From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: yao@codesourcery.com (Yao Qi)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, arm] Consistent display of registers in corefile
Date: Fri, 14 Jan 2011 16:52:00 -0000 [thread overview]
Message-ID: <201101141645.p0EGjno1030098@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <4D2F2BF9.8010103@codesourcery.com> from "Yao Qi" at Jan 13, 2011 10:44:41 AM
Yao Qi wrote:
> * arm-tdep.c (arm_register_reggroup_p): FPS register is in
> save_reggroup, restore_reggroup and all_reggroup.
This is OK.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2011-01-14 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 13:37 Yao Qi
2010-12-10 14:46 ` Mark Kettenis
2010-12-10 15:07 ` Yao Qi
2010-12-13 2:57 ` Daniel Jacobowitz
2010-12-13 10:00 ` Yao Qi
2010-12-19 18:24 ` Daniel Jacobowitz
2010-12-20 2:29 ` Yao Qi
2010-12-20 3:09 ` Daniel Jacobowitz
2011-01-13 13:45 ` Yao Qi
2011-01-13 16:04 ` Ulrich Weigand
2011-01-13 16:47 ` Yao Qi
2011-01-14 16:52 ` Ulrich Weigand [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=201101141645.p0EGjno1030098@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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