From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] target/arm: Relax r13 restriction for ldrex/strex for v8.0
Date: Mon, 18 Nov 2019 21:02:17 +0100 [thread overview]
Message-ID: <59a944f9-45f0-b78f-6ec3-5e96fe804767@linaro.org> (raw)
In-Reply-To: <CAFEAcA_qF6e_4_7syRVomag31pMgX02=R7JJ7a5pW_r+MU-aaQ@mail.gmail.com>
On 11/18/19 6:53 PM, Peter Maydell wrote:
> On Mon, 18 Nov 2019 at 13:16, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> On 11/18/19 2:10 PM, Peter Maydell wrote:
>>>> /* We UNDEF for these UNPREDICTABLE cases. */
>>>> if (a->rn == 15 || a->rt == 15
>>>> - || (s->thumb && a->rt == 13)
>>>> + || (!ENABLE_ARCH_8 && s->thumb && a->rt == 13)
>>>> || (mop == MO_64
>>>> && (a->rt2 == 15 || a->rt == a->rt2
>>>> - || (s->thumb && a->rt2 == 13)))) {
>>>> + || (!ENABLE_ARCH_8 && s->thumb && a->rt2 == 13)))) {
>>>> unallocated_encoding(s);
>>>> return true;
>>>> }
>>>
>>> These cases for r13 are indeed no longer UNPREDICTABLE in
>>> v8A, but they are still marked as UNPREDICTABLE for v8M...
>>
>> Ho hum. I knew I should have looked at that doc as well...
>
> I would like to get this in for rc2 tomorrow, so I propose
> to squash in changes to give the following result (basically
> turning the ENABLE_ARCH_8 checks into checks on a new bool 'v8a'):
>
>
> diff --git a/target/arm/translate.c b/target/arm/translate.c
> index b285b23858e..4d5d4bd8886 100644
> --- a/target/arm/translate.c
> +++ b/target/arm/translate.c
> @@ -8927,15 +8927,17 @@ static bool trans_SWPB(DisasContext *s, arg_SWP *a)
> static bool op_strex(DisasContext *s, arg_STREX *a, MemOp mop, bool rel)
> {
> TCGv_i32 addr;
> + /* Some cases stopped being UNPREDICTABLE in v8A (but not v8M) */
> + bool v8a = ENABLE_ARCH_8 && !arm_dc_feature(s, ARM_FEATURE_M);
Sorry, I wrote the patch but got distracted with other bugs without getting
around to posting. I had solved this with a new ENABLE_ARCH_8A, but this
version works for me as well.
Thanks,
r~
next prev parent reply other threads:[~2019-11-18 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 9:06 [PATCH for-4.2 0/2] target/arm: two fixes for ldrex/strex Richard Henderson
2019-11-17 9:06 ` [PATCH 1/2] target/arm: Do not reject rt == rt2 for strexd Richard Henderson
2019-11-18 13:17 ` Peter Maydell
2019-11-17 9:06 ` [PATCH 2/2] target/arm: Relax r13 restriction for ldrex/strex for v8.0 Richard Henderson
2019-11-18 13:10 ` Peter Maydell
2019-11-18 13:15 ` Richard Henderson
2019-11-18 17:53 ` Peter Maydell
2019-11-18 20:02 ` Richard Henderson [this message]
2019-11-18 21:22 ` Peter Maydell
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=59a944f9-45f0-b78f-6ec3-5e96fe804767@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).