From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH 0/3] tcg-optimize with known-zero bits
Date: Fri, 11 Jan 2013 15:42:50 -0800 [thread overview]
Message-ID: <1357947773-31051-1-git-send-email-rth@twiddle.net> (raw)
This patch set is extracted from Paolo's target-i386 eflags2
optimization branch:
git://github.com/bonzini/qemu.git eflags2
I've cherry-picked 3 patches and rebased them vs master. I've
made a few trivial changes to the patches:
* Extracting reset_all_temps as a function,
* Fixing a few type errors wrt target_ulong vs tcg_target_ulong.
While these were written in support of the other changes that
Paolo made wrt target-i386 eflags computation, they're not
dependent on them, and I think they should be considered for
inclusion regardless.
r~
Paolo Bonzini (3):
optimize: only write to state when clearing optimizer data
optimize: track nonzero bits of registers
optimize: optimize using nonzero bits
tcg/optimize.c | 177 ++++++++++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 150 insertions(+), 27 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-01-11 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 23:42 Richard Henderson [this message]
2013-01-11 23:42 ` [Qemu-devel] [PATCH 1/3] optimize: only write to state when clearing optimizer data Richard Henderson
2013-01-11 23:42 ` [Qemu-devel] [PATCH 2/3] optimize: track nonzero bits of registers Richard Henderson
2013-01-11 23:42 ` [Qemu-devel] [PATCH 3/3] optimize: optimize using nonzero bits Richard Henderson
2013-01-12 7:55 ` [Qemu-devel] [PATCH 0/3] tcg-optimize with known-zero bits Paolo Bonzini
2013-01-19 13:58 ` 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=1357947773-31051-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=aurelien@aurel32.net \
--cc=pbonzini@redhat.com \
--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).