qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: Remove redundant pointer from TCGContext
Date: Thu, 04 Oct 2012 14:39:43 -0700	[thread overview]
Message-ID: <506E021F.10500@twiddle.net> (raw)
In-Reply-To: <1349375342-18014-1-git-send-email-sw@weilnetz.de>

On 10/04/2012 11:29 AM, Stefan Weil wrote:
> The pointer entry 'temps' always refers to the array entry 'static_temps'.
> Removing the pointer and renaming 'static_temps' to 'temps' reduces the
> size of TCGContext (4 or 8 byte) and allows better code generation.
> 
> Signed-off-by: Stefan Weil <sw@weilnetz.de>

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


r~

  reply	other threads:[~2012-10-04 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 18:29 [Qemu-devel] [PATCH] tcg: Remove redundant pointer from TCGContext Stefan Weil
2012-10-04 21:39 ` Richard Henderson [this message]
2012-10-07 18:43 ` Blue Swirl

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=506E021F.10500@twiddle.net \
    --to=rth@twiddle.net \
    --cc=blauwirbel@gmail.com \
    --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).