qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/6] tcg: Introduce constraint for zero register
Date: Sat, 15 Feb 2025 12:06:48 -0800	[thread overview]
Message-ID: <3689674a-fa0a-4a9b-a447-8d706d7e3e4d@linaro.org> (raw)
In-Reply-To: <20250212034617.1079324-1-richard.henderson@linaro.org>

On 2/11/25 19:46, Richard Henderson wrote:
> Based-on:20250205040341.2056361-1-richard.henderson@linaro.org
> ("[PATCH 00/11] tcg: Cleanups after disallowing 64-on-32")
> 
> Introduce a new general-purpose constraint which maps 0
> to TCG_REG_ZERO, if defined.  This differs from existing
> constant constraints in that const_arg[*] is recorded as
> false, indicating that the value is in a register.
> 
> This doesn't make much difference to the current tree, but as a
> prelude to [1], where small output functions are categorized by
> register vs immediate arguments, then this provides a way to
> send a constant zero as a register argument.
> 
> 
> r~
> 
> 
> [1]https://patchew.org/QEMU/20250107080112.1175095-1-richard.henderson@linaro.org/
> 
> Richard Henderson (6):
>    tcg: Introduce the 'z' constraint for a hardware zero register
>    tcg/aarch64: Use 'z' constraint
>    tcg/loongarch64: Use 'z' constraint
>    tcg/mips: Use 'z' constraint
>    tcg/riscv: Use 'z' constraint
>    tcg/sparc64: Use 'z' constraint

Queued.


r~


      parent reply	other threads:[~2025-02-15 20:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  3:46 [PATCH 0/6] tcg: Introduce constraint for zero register Richard Henderson
2025-02-12  3:46 ` [PATCH 1/6] tcg: Introduce the 'z' constraint for a hardware " Richard Henderson
2025-02-13 15:45   ` Philippe Mathieu-Daudé
2025-02-13 17:15     ` Richard Henderson
2025-02-12  3:46 ` [PATCH 2/6] tcg/aarch64: Use 'z' constraint Richard Henderson
2025-02-16 13:06   ` Philippe Mathieu-Daudé
2025-02-12  3:46 ` [PATCH 3/6] tcg/loongarch64: " Richard Henderson
2025-02-13 15:47   ` Philippe Mathieu-Daudé
2025-02-12  3:46 ` [PATCH 4/6] tcg/mips: " Richard Henderson
2025-02-13 15:47   ` Philippe Mathieu-Daudé
2025-02-12  3:46 ` [PATCH 5/6] tcg/riscv: " Richard Henderson
2025-02-13 15:50   ` Philippe Mathieu-Daudé
2025-02-13 15:54     ` Philippe Mathieu-Daudé
2025-02-12  3:46 ` [PATCH 6/6] tcg/sparc64: " Richard Henderson
2025-02-13 15:53   ` Philippe Mathieu-Daudé
2025-02-15 20:06 ` 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=3689674a-fa0a-4a9b-a447-8d706d7e3e4d@linaro.org \
    --to=richard.henderson@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).