From: "Terry Guo" <terry.guo@arm.com>
To: "'Pedro Alves'" <palves@redhat.com>,
"Jonathan Larmour" <jifl@eCosCentric.com>
Cc: <gdb-patches@sourceware.org>, <yao@codesourcery.com>,
"Joey Ye" <Joey.Ye@arm.com>,
"Matthew Gretton-Dann" <Matthew.Gretton-Dann@arm.com>
Subject: RE: Fwd: Re: [patch] Add support for ARMv7M devices.
Date: Mon, 16 Apr 2012 07:56:00 -0000 [thread overview]
Message-ID: <001c01cd1ba6$44a2bf50$cde83df0$@guo@arm.com> (raw)
In-Reply-To: <4F59ED15.1030109@redhat.com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Friday, March 09, 2012 7:44 PM
> To: Jonathan Larmour
> Cc: gdb-patches@sourceware.org
> Subject: Re: Fwd: Re: [patch] Add support for ARMv7M devices.
>
> On 03/09/2012 04:24 AM, Jonathan Larmour wrote:
>
> > Over a year ago, after discussion and some helpful pointers from
> Daniel, I
> > submitted this patch:
> >
> > http://sourceware.org/ml/gdb-patches/2010-11/msg00142.html
> >
> > Unfortunately it fell by the wayside.
> >
> > This issue is coming to a head for the eCos project as we are
> updating our
> > ARM toolchain (we avoid the bleeding edge). However that means we
> really
> > need GDB to preserve backward compatibility, which it presently fails
> to do.
> >
> > We don't want to break backward compatibility with installed GDB
> stubs,
>
> > and the XML solution is complicated for users, opaque, not really
> suitable
>
> > for Eclipse (although there may be proprietary plugins around which
> try to
> > solve this, that isn't relevant for public GDB). Most importantly the
> > attached patch should flexibly work everywhere, and not break
> anyone's
> > compatibility. And furthermore, it allows us a clean migration path
> to the
> > changed 'g' packet length.
> >
> > So I'm attaching an updated version of the patch for current GDB
> trunk. If
> > it helps, I do have an FSF assignment and, from prehistory, commit
> > permissions.
>
>
> 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.
>
> 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.
>
> --
> Pedro Alves
Hi,
Sorry for bringing it back.
Can somebody please tell me how the "guess" mechanism works? How can the
buf_len in function process_g_packet become correct with "guess"?
Can we just make the arm-with-m.xml always include unnamed FPA registers? So
that it can cope with the case with or without FPA registers.
Thanks.
Terry
next prev parent reply other threads:[~2012-04-16 7:54 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
2012-03-09 16:06 ` Pedro Alves
2012-04-16 7:56 ` Terry Guo [this message]
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='001c01cd1ba6$44a2bf50$cde83df0$@guo@arm.com' \
--to=terry.guo@arm.com \
--cc=Joey.Ye@arm.com \
--cc=Matthew.Gretton-Dann@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jifl@eCosCentric.com \
--cc=palves@redhat.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