From: Simon Marchi <simon.marchi@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] arm-tdep.c: Refactor arm_process_displaced_insn
Date: Thu, 11 Feb 2016 16:59:00 -0000 [thread overview]
Message-ID: <56BCBDE9.1010106@ericsson.com> (raw)
In-Reply-To: <86oabnpk4r.fsf@gmail.com>
On 16-02-11 06:21 AM, Yao Qi wrote:
> Simon Marchi <simon.marchi@ericsson.com> writes:
>
>> - if ((insn & 0xf0000000) == 0xf0000000)
>> - err = arm_decode_unconditional (gdbarch, insn, regs, dsc);
>> - else switch (((insn & 0x10) >> 4) | ((insn & 0xe000000) >> 24))
>> + cond = bits (insn, 28, 31);
>
> Variable 'cond' is only used once, so don't need to define it. This is
> my personal flavour.
Well, my goal was to use variables with names that refer to these tables:
http://nova.polymtl.ca/~simark/ss/fileJVxJNx.png
(ARM Architecture Reference Manual, section A5.1)
If you only use the bits (insn, 28, 31) notation, I think you lose readability,
because the you have to do one more indirection in the doc, to go see what those
bits mean.
>> + op1 = bits (insn, 25, 27);
>> + op = bit (insn, 4);
>> +
>> + if (cond != 0xf)
>
> if (bits (insn, 28, 31) != INST_NV)
>
> this is consistent with other places in arm-tdep.c
I agree, if there is a define for that it should be used. What does _NV stand
for though?
>> {
>> - case 0x0: case 0x1: case 0x2: case 0x3:
>> - err = arm_decode_dp_misc (gdbarch, insn, regs, dsc);
>> - break;
>> + switch (op1)
>> + {
>> + case 0x0:
>> + case 0x1:
>> + -/* Data-processing and miscellaneous instructions */
>> + err = arm_decode_dp_misc (gdbarch, insn, regs, dsc);
>> + break;
>>
>> - case 0x4: case 0x5: case 0x6:
>> - err = arm_decode_ld_st_word_ubyte (gdbarch, insn, regs, dsc);
>> - break;
>> + case 0x2:
>> + /* Load/store word and unsigned byte */
>> + err = arm_decode_ld_st_word_ubyte (gdbarch, insn, regs, dsc);
>> + break;
>>
>> - case 0x7:
>> - err = arm_decode_media (gdbarch, insn, dsc);
>> - break;
>> + case 0x3:
>> + if (op == 0)
>
> 'op' is only used here, let us define it in this block, or use
> 'bit (insn, 4)' instead.
Ok for moving it, but I would suggest keeping the variable op, for
the same reason as cond mentioned above.
Thanks,
Simon
next prev parent reply other threads:[~2016-02-11 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 16:17 [PATCH 0/3] Minor refactorings in arm-tdep.c instruction decoding Simon Marchi
2016-02-10 16:17 ` [PATCH 3/3] arm-tdep.c: Refactor arm_decode_media Simon Marchi
2016-02-11 11:58 ` Yao Qi
2016-02-10 16:17 ` [PATCH 2/3] arm-tdep.c: Refactor arm_decode_dp_misc Simon Marchi
2016-02-11 11:52 ` Yao Qi
2016-02-11 17:10 ` Yao Qi
2016-02-11 17:18 ` Simon Marchi
2016-02-10 16:17 ` [PATCH 1/3] arm-tdep.c: Refactor arm_process_displaced_insn Simon Marchi
2016-02-11 11:22 ` Yao Qi
2016-02-11 16:59 ` Simon Marchi [this message]
2016-02-12 16:56 ` Yao Qi
2016-02-11 11:17 ` [PATCH 0/3] Minor refactorings in arm-tdep.c instruction decoding Yao Qi
2016-02-16 15:26 ` Simon Marchi
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=56BCBDE9.1010106@ericsson.com \
--to=simon.marchi@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