From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 3/5] tcg/sparc: Use the constant pool for 64-bit constants
Date: Sat, 5 Feb 2022 07:41:40 +1100 [thread overview]
Message-ID: <0c47260f-7ecc-7b67-4d29-4e9b8c3cdabc@linaro.org> (raw)
In-Reply-To: <CAFEAcA8YyrASZw7Wj1c5fLg-60KUKPsC7eVA8+YhNTsVM4t2kg@mail.gmail.com>
On 2/5/22 05:18, Peter Maydell wrote:
> On Fri, 4 Feb 2022 at 07:53, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> tcg/sparc/tcg-target.c.inc | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>> diff --git a/tcg/sparc/tcg-target.c.inc b/tcg/sparc/tcg-target.c.inc
>> index 6349f750cc..47bdf314a0 100644
>> --- a/tcg/sparc/tcg-target.c.inc
>> +++ b/tcg/sparc/tcg-target.c.inc
>> @@ -332,6 +332,13 @@ static bool patch_reloc(tcg_insn_unit *src_rw, int type,
>> insn &= ~INSN_OFF19(-1);
>> insn |= INSN_OFF19(pcrel);
>> break;
>> + case R_SPARC_13:
>> + if (!check_fit_ptr(value, 13)) {
>> + return false;
>> + }
>
> This code seems to contemplate that the offset might not fit
> into the 13-bit immediate field (unlike the other two reloc
> cases in this function, which just assert() that it fits)...
Ooo, thanks for noticing. The other entries have not been updated for changes to tcg
relocations. They should be returning false instead of asserting.
Returning false here tells generic code the relocation didn't fit, and to restart the TB
with half of the number of guest instructions.
>> + /* Use the constant pool, if possible. */
>> + if (!in_prologue && USE_REG_TB) {
>> + new_pool_label(s, arg, R_SPARC_13, s->code_ptr,
>> + tcg_tbrel_diff(s, NULL));
>> + tcg_out32(s, LDX | INSN_RD(ret) | INSN_RS1(TCG_REG_TB));
>> + return;
>> + }
>
> ...but this code doesn't seem to have any mechanism for
> falling back to something else if it won't fit.
It will fit, because we'll keep trying with smaller TBs until it does. If for some reason
a target generates more than 8k for a single guest insn... it will go boom.
r~
next prev parent reply other threads:[~2022-02-04 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:00 [PATCH v4 0/5] tcg/sparc: Unaligned access for user-only Richard Henderson
2022-02-04 7:00 ` [PATCH v4 1/5] tcg/sparc: Add scratch argument to tcg_out_movi_int Richard Henderson
2022-02-04 17:35 ` Peter Maydell
2022-02-04 20:42 ` Richard Henderson
2022-02-04 7:00 ` [PATCH v4 2/5] tcg/sparc: Improve code gen for shifted 32-bit constants Richard Henderson
2022-02-04 7:56 ` Philippe Mathieu-Daudé via
2022-02-04 17:39 ` Peter Maydell
2022-02-04 7:00 ` [PATCH v4 3/5] tcg/sparc: Use the constant pool for 64-bit constants Richard Henderson
2022-02-04 18:18 ` Peter Maydell
2022-02-04 20:41 ` Richard Henderson [this message]
2022-02-04 22:20 ` Peter Maydell
2022-02-04 7:00 ` [PATCH v4 4/5] tcg/sparc: Add tcg_out_jmpl_const for better tail calls Richard Henderson
2022-02-04 18:34 ` Peter Maydell
2022-02-04 20:44 ` Richard Henderson
2022-02-04 7:00 ` [PATCH v4 5/5] tcg/sparc: Support unaligned access for user-only Richard Henderson
2022-02-04 19:07 ` Peter Maydell
2022-02-04 20:55 ` Richard Henderson
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=0c47260f-7ecc-7b67-4d29-4e9b8c3cdabc@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@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).