Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Richard Earnshaw <rearnsha@arm.com>, Yao Qi <yao@codesourcery.com>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	       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, 20 Aug 2014 17:36:00 -0000	[thread overview]
Message-ID: <53F4DC74.8080807@redhat.com> (raw)
In-Reply-To: <53EB7965.8070208@arm.com>

On 08/13/2014 03:42 PM, Richard Earnshaw wrote:
> On 13/08/14 13:39, Yao Qi wrote:
>> On 08/13/2014 08:25 PM, Philippe Waroquiers wrote:
>>> The 'it' in 'fix it' is ambiguous to me.
>>> Does the 'it' mean:
>>>      fix aarch64-core.xml to change cpsr to 32 bits ?
>>
>> That was what I meant, however ....
>>
>>> or does that confirm the initial proposal i.e.
>>>      fix e.g. aarch64.dat to change cpsr to 64 bits ?
>>
>> ... I find a patch changed cpsr to 64 bit in last Dec.
>>
>>  [PATCH] AARCH64: Change cpsr type to be 64bit.
>>  https://sourceware.org/ml/gdb-patches/2013-12/msg00720.html
>>
>> and looks aarch64.dat was not updated together in this patch.
>>
>> I am sure that aarch64.dat and aarch64-core.xml are not in sync,
>> but I don't know which way to go, sorry.
>>
> 
> Changing the XML doesn't sound like the right way forward, the XML can
> be embedded into other components as part of the register description
> interface.
> 
> Hmm, I can't see where anyone ever formally approved that change.  In
> fact, Mark K commented at the time:
> 
> "Basing GDB's fundamentals on a particular OS's ptrace(2)
> implementation is a bad idea."
> 
> So it seems to me that that change was indeed incorrect and should
> probably be reverted (at least in its current incarnation).

I agree, and I'm surprised to learn the patch went in.  :-/

Thanks,
Pedro Alves


  reply	other threads:[~2014-08-20 17:36 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
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 [this message]
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=53F4DC74.8080807@redhat.com \
    --to=palves@redhat.com \
    --cc=catalin.udma@freescale.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    --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