qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg/i386: allow constants in load/store ops
Date: Mon, 10 Sep 2012 06:40:09 -0700	[thread overview]
Message-ID: <1347284409.8336.3.camel@pebble.twiddle.home> (raw)
In-Reply-To: <1347278184-18693-1-git-send-email-aurelien@aurel32.net>

On Mon, 2012-09-10 at 13:56 +0200, Aurelien Jarno wrote:
> On x86, it is possible to move a constant value to memory. Add code to
> handle a constant argument to load/store ops.
> 
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net> 

While useful, you'll find that most constants that want storing to
memory are not generated with store opcodes, but directly via
tcg_out_st.  As happens for all register spilling, and helper calls.

Reviewed-by: Richard Henderson <rth@twiddle.net>


r~

  reply	other threads:[~2012-09-10 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 11:56 [Qemu-devel] [PATCH] tcg/i386: allow constants in load/store ops Aurelien Jarno
2012-09-10 13:40 ` Richard Henderson [this message]
2012-09-10 13:57   ` Aurelien Jarno

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=1347284409.8336.3.camel@pebble.twiddle.home \
    --to=rth@twiddle.net \
    --cc=aurelien@aurel32.net \
    --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).