Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] New regs_info for aarch32
Date: Mon, 03 Aug 2015 16:34:00 -0000	[thread overview]
Message-ID: <55BF980F.5010306@gmail.com> (raw)
In-Reply-To: <55BF7383.5030304@redhat.com>



On 03/08/15 14:58, Pedro Alves wrote:
> Why weren't these moved as well?  At first,
>
>> >-  init_registers_arm_with_vfpv2 ();
>> >-  init_registers_arm_with_vfpv3 ();
>> >-  init_registers_arm_with_neon ();
>> >+
>> >+  initialize_low_arch_aarch32 ();
> I thought that this was because aarch64 doesn't
> do the old iwmmxt, but then in the following patch you
> have this anyway:

Yes, aarch64 doesn't support iwmmxt.

>
>> >  void
>> >  initialize_low_arch_aarch32 (void)
>> >  {
>> >+#ifndef __aarch64__
>> >    init_registers_arm_with_vfpv2 ();
>> >    init_registers_arm_with_vfpv3 ();
>> >+#endif
>> >    init_registers_arm_with_neon ();
>> >
> So I don't understand when/where to initialize arm32
> descriptions going forward.

Sorry, I am not sure I understand your question.

initialize_low_arch_aarch32 is called from
linux-arm-low.c and linux-aarch64-low.c for arm and aarch64
target respectively.  For aarch64, we initialize arm_with_neon
while for arm, we initialize arm_with_vfpv2 and arm_with_vfpv3
additionally.

-- 
Yao (齐尧)


  reply	other threads:[~2015-08-03 16:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 15:17 [PATCH 0/7] Aarch64 linux GDB remote multi-arch debugging Yao Qi
2015-07-31 15:16 ` [PATCH 1/7] Move have_ptrace_getregset to linux-low.c Yao Qi
2015-07-31 15:17 ` [PATCH 4/7] Get and set PC correctly on aarch64 in multi-arch Yao Qi
2015-07-31 15:17 ` [PATCH 2/7] New regs_info for aarch32 Yao Qi
2015-08-03 13:58   ` Pedro Alves
2015-08-03 16:34     ` Yao Qi [this message]
2015-08-03 17:11       ` Pedro Alves
2015-08-04  9:52         ` Yao Qi
2015-08-04 10:11           ` Pedro Alves
2015-08-11 19:40           ` Joel Brobecker
2015-08-18 15:21             ` Yao Qi
2015-08-18 22:42               ` Joel Brobecker
2015-07-31 15:17 ` [PATCH 5/7] Disable Z0 packet on aarch64 on multi-arch debugging Yao Qi
2015-07-31 15:17 ` [PATCH 6/7] Disable tracepoint support for aarch32 Yao Qi
2015-07-31 15:17 ` [PATCH 3/7] Use arm target description and regs_info for 32-bit file on aarch64 GDBserver Yao Qi
2015-08-04 13:44   ` Yao Qi
2015-07-31 15:17 ` [PATCH 7/7] Mention multi-arch debugging support in NEWS Yao Qi
2015-08-19  8:26   ` Yao Qi
2015-09-04 14:30   ` Yao Qi
2015-08-03 14:00 ` [PATCH 0/7] Aarch64 linux GDB remote multi-arch debugging Pedro Alves
2015-08-04 13:41   ` Yao Qi

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=55BF980F.5010306@gmail.com \
    --to=qiyaoltc@gmail.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