Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Generalize gdb.reverse/aarch64.exp
Date: Wed, 24 Feb 2016 19:37:00 -0000	[thread overview]
Message-ID: <56CE066D.4010709@redhat.com> (raw)
In-Reply-To: <1456324818-25547-1-git-send-email-yao.qi@linaro.org>

On 02/24/2016 02:40 PM, Yao Qi wrote:
> I said we can generialize gdb.reverse/aarch64.exp for other
> architectures https://sourceware.org/ml/gdb-patches/2015-05/msg00482.html
> and here is the patch to change aarch64.exp so that it can be used to
> test for other architectures as well.
> 
> gdb/testsuite:
> 
> 2016-02-24  Yao Qi  <yao.qi@linaro.org>
> 
> 	* gdb.reverse/aarch64.c: [__aarch64__] Include arm_neon.h.
> 	(testcase_ftype): New.
> 	(testcases): New array.
> 	(n_testcases): New.
> 	(main): Call each element in testcases.
> 	* gdb.reverse/aarch64.exp: Remove is_aarch64_target check.
> 	(read_testcase): New.
> 	Do the tests in a loop.

Thanks for splitting.  LGTM.

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-02-24 19:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 16:53 [PATCH 0/3] Bug fixes in arm reverse debugging Yao Qi
2016-02-22 16:53 ` [PATCH 1/3] Generalize gdb.reverse/aarch64.exp Yao Qi
2016-02-24 11:22   ` Pedro Alves
2016-02-24 14:40     ` Yao Qi
2016-02-24 14:40       ` [PATCH 1.5/3] Rename gdb.reverse/aarch64.{exp,c} to gdb.reverse/insn-reverse.{exp,c} Yao Qi
2016-02-24 19:37       ` Pedro Alves [this message]
2016-02-22 16:53 ` [PATCH 3/3] Fix various bugs in arm_record_exreg_ld_st_insn Yao Qi
2016-02-23 19:59   ` Luis Machado
2016-02-26 14:54     ` Yao Qi
2016-02-22 16:53 ` [PATCH 2/3] Record right reg num of thumb special data instructions Yao Qi
2016-02-26 15:01 ` [PATCH 0/3] Bug fixes in arm reverse debugging 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=56CE066D.4010709@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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