From: Sven Schnelle <svens@stackframe.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Helge Deller <deller@gmx.de>, qemu-devel@nongnu.org
Subject: Re: target/hppa: be,n nullifying first insn at branch target?
Date: Tue, 26 Mar 2024 17:52:54 +0100 [thread overview]
Message-ID: <87r0fxyly1.fsf@t14.stackframe.org> (raw)
In-Reply-To: <bcbf8200-1ffa-4a39-b7b5-e19a65257962@linaro.org> (Richard Henderson's message of "Mon, 25 Mar 2024 19:20:34 -1000")
Richard Henderson <richard.henderson@linaro.org> writes:
> On 3/25/24 09:33, Sven Schnelle wrote:
>> diff --git a/target/hppa/translate.c b/target/hppa/translate.c
>> index 7546a5f5a2..56c68a7cbe 100644
>> --- a/target/hppa/translate.c
>> +++ b/target/hppa/translate.c
>> @@ -3847,7 +3849,7 @@ static bool trans_be(DisasContext *ctx, arg_be *a)
>> copy_iaoq_entry(ctx, cpu_gr[31], ctx->iaoq_n, ctx->iaoq_n_var);
>> tcg_gen_mov_i64(cpu_sr[0], cpu_iasq_b);
>> }
>> - if (a->n && use_nullify_skip(ctx)) {
>> + if (0 && a->n && use_nullify_skip(ctx)) {
>> copy_iaoq_entry(ctx, cpu_iaoq_f, -1, tmp);
>> tcg_gen_addi_i64(tmp, tmp, 4);
>> copy_iaoq_entry(ctx, cpu_iaoq_b, -1, tmp);
>> So i think the problem is caused by this optimization. Does this
>> ring a
>> bell? Debugging this is rather hard, alone the logfile above is 6GB in
>> size...
>
> The problem is a missing
>
> nullify_set(ctx, 0)
>
> within this block.
>
> I have patches queued to reorg the IAQ handling, which I hope will fix
> the problem Sven saw with spaces. It would fix this as a consequence
> of other unification. But I think it's a bit too big for 9.0.
Thanks Richard. Let me know if you want me to test patches.
prev parent reply other threads:[~2024-03-26 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 19:33 target/hppa: be,n nullifying first insn at branch target? Sven Schnelle
2024-03-26 5:20 ` Richard Henderson
2024-03-26 16:52 ` Sven Schnelle [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=87r0fxyly1.fsf@t14.stackframe.org \
--to=svens@stackframe.org \
--cc=deller@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).