From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org,
patches@linaro.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 1/2] xen/arm: Start to implement an ARM decoder instruction
Date: Wed, 31 Jul 2013 17:39:30 +0100 [thread overview]
Message-ID: <51F93DC2.1030606@linaro.org> (raw)
In-Reply-To: <1375287993.7382.115.camel@kazak.uk.xensource.com>
On 07/31/2013 05:26 PM, Ian Campbell wrote:
> On Wed, 2013-07-31 at 17:18 +0100, Julien Grall wrote:
>
>
>>>> + switch ( opB & 0x3 )
>>>> + {
>>>> + case 0:
>>>> + dabt->size = 2;
>>>> + break;
>>>> + case 1:
>>>> + dabt->size = 1;
>>>
>>> ->sign is uninitialised for these two cases?
>>>
>>> Actually, for many of them I think?
>>
>> I plan to zeroed the ISS field (ie sign, reg...) by default. See TODO in
>> decode_instruction. Do I still need to set sign to 0?
>
> Well, you need to at least do one or the other!
>
> Even if you are zeroing the iss be default I think it would be useful
> from a documentation/clarity perspective to set it explicitly to zero.
There is only few functions which deal with signed-register. So if we
add a line "dabt->sign = 0" it's less clear. What about a helper?
update_dabt(struct hsr_dabt *dabt, uint16_t reg, uint8_t size,
bool_t sign)
--
Julien
next prev parent reply other threads:[~2013-07-31 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 14:49 [PATCH v3 0/2] Implement errata 766422 Julien Grall
2013-07-31 14:49 ` [PATCH v3 1/2] xen/arm: Start to implement an ARM decoder instruction Julien Grall
2013-07-31 15:34 ` Ian Campbell
2013-07-31 16:18 ` Julien Grall
2013-07-31 16:26 ` Ian Campbell
2013-07-31 16:39 ` Julien Grall [this message]
2013-08-01 14:31 ` Ian Campbell
2013-07-31 14:49 ` [PATCH v3 2/2] xen/arm: errata 766422: decode thumb store during data abort Julien Grall
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=51F93DC2.1030606@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=patches@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).