From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] Add unit test to aarch64 prologue analyzer
Date: Tue, 29 Nov 2016 14:58:00 -0000 [thread overview]
Message-ID: <wwokbmwyxrit.fsf@ericsson.com> (raw)
In-Reply-To: <1480428758-2481-1-git-send-email-yao.qi@linaro.org>
Yao Qi writes:
> @@ -436,6 +461,89 @@ aarch64_analyze_prologue (struct gdbarch *gdbarch,
> return start;
> }
>
> +static CORE_ADDR
> +aarch64_analyze_prologue (struct gdbarch *gdbarch,
> + CORE_ADDR start, CORE_ADDR limit,
> + struct aarch64_prologue_cache *cache)
> +{
> + instruction_reader reader { };
> +
Could we use the default constructor here? If it's kept.
> + return aarch64_analyze_prologue (gdbarch, start, limit, cache,
> + reader);
> +}
> +
> +#if GDB_SELF_TEST
> +
> +namespace selftests {
> +
> + /* Instruction reader from manually cooked instruction sequences. */
> + class instruction_reader_test : public abstract_instruction_reader
> + {
> + public:
> + instruction_reader_test() = default ;
Very nit, but there's a space before ';'
Also I wonder if we need to specify the default constructor explicitly ?
Is there a rationale for it?
It's never used too, unless you apply my previous comment.
next prev parent reply other threads:[~2016-11-29 14:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 14:12 Yao Qi
2016-11-29 14:12 ` [PATCH 2/2] [AArch64] Recognize STR instruction in prologue Yao Qi
2016-11-30 18:33 ` Pedro Alves
2016-11-29 14:58 ` Antoine Tremblay [this message]
2016-11-30 11:15 ` [PATCH 1/2] Add unit test to aarch64 prologue analyzer Yao Qi
2016-11-30 11:53 ` Antoine Tremblay
2016-11-30 16:35 ` Yao Qi
2016-11-30 16:42 ` Antoine Tremblay
2016-11-30 18:16 ` Pedro Alves
2016-11-30 18:29 ` Pedro Alves
2016-11-30 18:38 ` Pedro Alves
2016-11-30 19:30 ` Luis Machado
2016-12-01 12:53 ` Pedro Alves
2016-12-01 11:17 ` [PATCH 1/2 v2] " Yao Qi
2016-12-01 11:17 ` [PATCH 2/2 v2] [AArch64] Recognize STR instruction in prologue Yao Qi
2016-12-01 13:07 ` Pedro Alves
2016-12-02 9:42 ` Yao Qi
2016-12-01 12:57 ` [PATCH 1/2 v2] Add unit test to aarch64 prologue analyzer Pedro Alves
2016-12-01 15:21 ` Yao Qi
2016-12-01 16:04 ` Yao Qi
2016-12-01 18:05 ` Pedro Alves
2016-12-02 9:40 ` Yao Qi
2016-12-02 11:11 ` 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=wwokbmwyxrit.fsf@ericsson.com \
--to=antoine.tremblay@ericsson.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