From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE
Date: Thu, 17 Apr 2008 17:47:00 -0000 [thread overview]
Message-ID: <20080417172801.GM17488@caradoc.them.org> (raw)
In-Reply-To: <200802281657.m1SGv67A001187@d12av02.megacenter.de.ibm.com>
On Thu, Feb 28, 2008 at 05:57:06PM +0100, Ulrich Weigand wrote:
> - There was a conditional check for fpscr in ppc_cannot_store_register;
> but as this routine is never called for fpscr in SPE mode, the check
> seems superfluous and I just removed it.
This doesn't seem to be true.
gdbserver: Unknown register fpscr requested
There's no code to use PPC_PTRACE_GETREGS, so we do in fact reach
here. I'm retesting with
/* Some kernels do not allow us to store fpscr. */
if (!(ppc_hwcap & PPC_FEATURE_HAS_SPE) && regno == find_regno ("fpscr"))
return 2;
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-17 17:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 1:11 [rfc][3/3] gdbserver bi-arch for ppc: enable bi-arch support Ulrich Weigand
2008-02-27 13:20 ` Daniel Jacobowitz
2008-02-28 7:16 ` Ulrich Weigand
2008-02-28 14:13 ` Daniel Jacobowitz
2008-02-28 17:03 ` [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE Ulrich Weigand
2008-02-28 17:12 ` Daniel Jacobowitz
2008-03-26 20:21 ` Ulrich Weigand
2008-04-19 0:19 ` Thiago Jung Bauermann
2008-04-19 6:17 ` Daniel Jacobowitz
2008-04-20 14:28 ` Thiago Jung Bauermann
2008-04-21 9:21 ` Daniel Jacobowitz
2008-04-21 10:00 ` Thiago Jung Bauermann
2008-04-21 14:04 ` Ulrich Weigand
2008-04-21 14:32 ` Daniel Jacobowitz
2008-04-21 15:36 ` Ulrich Weigand
2008-04-21 15:38 ` Daniel Jacobowitz
2008-04-17 17:47 ` Daniel Jacobowitz [this message]
2008-04-17 19:03 ` Daniel Jacobowitz
2008-04-17 21:34 ` Ulrich Weigand
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=20080417172801.GM17488@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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