Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Yao Qi <yao@codesourcery.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
	Catalin Udma <catalin.udma@freescale.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] aarch64/gdbserver: fix floating point registers display
Date: Wed, 13 Aug 2014 12:24:00 -0000	[thread overview]
Message-ID: <1407932734.2182.67.camel@soleil> (raw)
In-Reply-To: <53E9EB9A.7000304@codesourcery.com>

On Tue, 2014-08-12 at 18:25 +0800, Yao Qi wrote:
> On 08/12/2014 05:43 PM, Richard Earnshaw wrote:
> > This doesn't seem right to me.  The CPSR is a 32-bit register, not a
> > 64-bit one.
> 
> cpsr is 64-bit in the target description, see
> gdb/features/aarch64-core.xml,
> 
>   <reg name="cpsr" bitsize="64"/>
> 
> We need to fix it.
The 'it' in 'fix it' is ambiguous to me.
Does the 'it' mean:
     fix aarch64-core.xml to change cpsr to 32 bits ?
or does that confirm the initial proposal i.e.
     fix e.g. aarch64.dat to change cpsr to 64 bits ?

Philippe
(following the discussion, to update Valgrind aarch64 gdbserver
accordingly)


  reply	other threads:[~2014-08-13 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  9:23 Catalin Udma
2014-08-12  9:43 ` Richard Earnshaw
2014-08-12 10:29   ` Yao Qi
2014-08-13 12:24     ` Philippe Waroquiers [this message]
2014-08-13 12:43       ` catalin.udma
     [not found]       ` <53EB5C86.4030307@codesourcery.com>
2014-08-13 14:42         ` Richard Earnshaw
2014-08-20 17:36           ` Pedro Alves
2014-08-21  6:54             ` catalin.udma
2014-08-21  6:56               ` Andrew Pinski
2014-08-21  7:30                 ` Yao Qi
2014-08-21 16:05                   ` Pedro Alves
2014-10-01  9:51                     ` Pedro Alves
2014-10-06  9:06                       ` catalin.udma
2014-10-06 12:28                         ` 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=1407932734.2182.67.camel@soleil \
    --to=philippe.waroquiers@skynet.be \
    --cc=catalin.udma@freescale.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rearnsha@arm.com \
    --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