From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: sw@weilnetz.de
Subject: Re: [PATCH 0/2] tcg/tci: Two regression fixes
Date: Tue, 6 Jun 2023 22:53:37 -0700 [thread overview]
Message-ID: <98d56274-c104-3ca5-1e03-b149c953c1c6@linaro.org> (raw)
In-Reply-To: <20230607054654.622010-1-richard.henderson@linaro.org>
On 6/6/23 22:46, Richard Henderson wrote:
> Two recent regressions, both related to recent tcg changes.
>
> Our CI does not test TCI with --enable-debug-tcg, which given timeout
> constraints is probably correct, but in this case resulted in an
> infinite loop on aarch64 multiarch/memory.c with FEAT_LSE2 enabled.
To expand on that: with --enable-debug-tcg, assertions fire and catch the bug; without the
assertions, the generated bytecode is incorrect, which leads to the loop.
r~
prev parent reply other threads:[~2023-06-07 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 5:46 [PATCH 0/2] tcg/tci: Two regression fixes Richard Henderson
2023-06-07 5:46 ` [PATCH 1/2] tcg/tci: Adjust passing of MemOpIdx Richard Henderson
2023-06-07 5:46 ` [PATCH 2/2] tcg/tci: Adjust call-clobbered regs for int128_t Richard Henderson
2023-06-07 7:44 ` Philippe Mathieu-Daudé
2023-06-07 5:53 ` Richard Henderson [this message]
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=98d56274-c104-3ca5-1e03-b149c953c1c6@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).