From: "Andreas Färber" <afaerber@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH] tcg: Remove temp_buf
Date: Fri, 19 Apr 2013 14:11:15 +0200 [thread overview]
Message-ID: <51713463.4080300@suse.de> (raw)
In-Reply-To: <1366360066-3373-1-git-send-email-rth@twiddle.net>
Hi,
Am 19.04.2013 10:27, schrieb Richard Henderson:
> All targets have been converted to allocating space for temporaries
> on the stack. No need to allocate space within the CPU_COMMON block.
>
> Signed-off-by: Richard Henderson <rth@twiddle.net>
> ---
> This depends on my tcg-arm patch set that's still outstanding.
My tree still has exactly one user in tcg/arm/, so once that disappears
feel free to add my Reviewed-by. Thanks for helping clean this up!
One question...
>
>
> r~
> ---
> include/exec/cpu-defs.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include/exec/cpu-defs.h b/include/exec/cpu-defs.h
> index d8c64e9..41f5b32 100644
> --- a/include/exec/cpu-defs.h
> +++ b/include/exec/cpu-defs.h
> @@ -152,8 +152,6 @@ typedef struct CPUWatchpoint {
> memory was accessed */ \
> CPU_COMMON_TLB \
> struct TranslationBlock *tb_jmp_cache[TB_JMP_CACHE_SIZE]; \
> - /* buffer for temporaries in the code generator */ \
> - long temp_buf[CPU_TEMP_BUF_NLONGS]; \
Could CPU_TEMP_BUF_NLONGS be removed, too?
Andreas
> \
> int64_t icount_extra; /* Instructions until next timer event. */ \
> /* Number of cycles left, with interrupt flag in high bit. \
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-04-19 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 8:27 [Qemu-devel] [PATCH] tcg: Remove temp_buf Richard Henderson
2013-04-19 12:11 ` Andreas Färber [this message]
2013-04-19 12:18 ` Andreas Färber
2013-04-20 10:46 ` Blue Swirl
2013-04-20 17:00 ` Richard Henderson
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=51713463.4080300@suse.de \
--to=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).