From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com
Subject: [Qemu-devel] [PATCH v4 0/5] Better allocation of code_gen_buffer
Date: Tue, 16 Oct 2012 17:30:09 +1000 [thread overview]
Message-ID: <1350372614-30041-1-git-send-email-rth@twiddle.net> (raw)
Changes v3->v4:
* Patch 5 actually included,
* Patch 1 updates printf format for changed size_t.
r~
Richard Henderson (5):
exec: Split up and tidy code_gen_buffer
exec: Don't make DEFAULT_CODE_GEN_BUFFER_SIZE too large
exec: Do not use absolute address hints for code_gen_buffer with
-fpie
exec: Allocate code_gen_prologue from code_gen_buffer
exec: Make MIN_CODE_GEN_BUFFER_SIZE private to exec.c
exec-all.h | 2 -
exec.c | 238 +++++++++++++++++++++++++++++++++----------------------------
tcg/tcg.h | 2 +-
3 files changed, 128 insertions(+), 114 deletions(-)
--
1.7.11.7
next reply other threads:[~2012-10-16 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:30 Richard Henderson [this message]
2012-10-16 7:30 ` [Qemu-devel] [PATCH 1/5] exec: Split up and tidy code_gen_buffer Richard Henderson
2012-10-16 7:30 ` [Qemu-devel] [PATCH 2/5] exec: Don't make DEFAULT_CODE_GEN_BUFFER_SIZE too large Richard Henderson
2012-10-16 7:30 ` [Qemu-devel] [PATCH 3/5] exec: Do not use absolute address hints for code_gen_buffer with -fpie Richard Henderson
2012-11-18 20:48 ` Stefan Weil
2012-11-19 16:27 ` Richard Henderson
2012-10-16 7:30 ` [Qemu-devel] [PATCH 4/5] exec: Allocate code_gen_prologue from code_gen_buffer Richard Henderson
2012-10-16 7:30 ` [Qemu-devel] [PATCH 5/5] exec: Make MIN_CODE_GEN_BUFFER_SIZE private to exec.c Richard Henderson
2012-10-20 8:47 ` [Qemu-devel] [PATCH v4 0/5] Better allocation of code_gen_buffer 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=1350372614-30041-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=blauwirbel@gmail.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).