Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fwd: Re: [patch] Add support for ARMv7M devices.
Date: Fri, 09 Mar 2012 15:53:00 -0000	[thread overview]
Message-ID: <4F5A2747.8070809@eCosCentric.com> (raw)
In-Reply-To: <4F59ED15.1030109@redhat.com>

On 09/03/12 11:44, Pedro Alves wrote:
> On 03/09/2012 04:24 AM, Jonathan Larmour wrote:
> I support this.  I wrote essentially the same without being aware of
> your patch: <http://sourceware.org/ml/gdb-patches/2011-04/msg00372.html>.
> 
> Wish I had seen yours before that.
> 
> If there are no other comments in a week or so, I say put this in.

I have noticed one slight practical difference with your patch... Mine used:
+  <xi:include href="arm-fpa.xml"/>

whereas yours enumerates all the FPA registers, but with the name set to
"", which is better - I hadn't been aware of that property of not showing
a reg if the name is empty.

> On 03/09/2012 04:24 AM, Jonathan Larmour wrote:
>>  	}
>> +      else
>> +        is_m = 0;
>>
> 
> I think this is unnecessary though.  The variable is initialized to 0.

True. I thought I needed to reset it if it got set further up, but now I
see that couldn't happen ( because !tdesc_has_registers in that case)

So perhaps should we just go with your version of the patch after all?
It's effectively identical other than the above FPA name improvement.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
      **  Visit us at the ESC Expo at Design West in San Jose  **
      **  27-29 March, McEnery Convention Center - Stand #846  **
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


  reply	other threads:[~2012-03-09 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  4:25 Jonathan Larmour
2012-03-09 11:44 ` Pedro Alves
2012-03-09 15:53   ` Jonathan Larmour [this message]
2012-03-09 16:06     ` Pedro Alves
2012-04-16  7:56   ` Terry Guo
2012-04-16 14:40     ` Jonathan Larmour
2012-04-17  4:06       ` Terry Guo
2012-03-09 15:39 ` Yao Qi
2012-03-09 16:13   ` Jonathan Larmour
2012-03-09 16:29     ` Pedro Alves
2012-03-11  3:37       ` Jonathan Larmour
2012-03-14 16:06         ` Pedro Alves
2012-03-15  6:27           ` Jonathan Larmour
2012-03-15 17:09             ` Pedro Alves
2012-03-15 18:33               ` Jonathan Larmour
2012-03-15 18:43                 ` Pedro Alves
2012-03-15 18:56                   ` Jonathan Larmour
2012-03-15 18:58                     ` 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=4F5A2747.8070809@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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