From: Aurelien Jarno <aurelien@aurel32.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] tcg: allocate memory to spill registers on startup
Date: Fri, 10 Apr 2009 16:56:09 +0200 [thread overview]
Message-ID: <20090410145609.GA20999@volta.aurel32.net> (raw)
In-Reply-To: <200904101544.56081.paul@codesourcery.com>
On Fri, Apr 10, 2009 at 03:44:55PM +0100, Paul Brook wrote:
> On Friday 10 April 2009, Aurelien Jarno wrote:
> > + assert(size != TCG_MAX_TEMPS * sizeof(tcg_target_long));
>
> Shouldn't this be >= ?
>
When I wrote that, I thought that the two sizes have to match, but you
are right, the frame size can actually be bigger.
Any other comment?
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2009-04-10 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 8:54 [Qemu-devel] [RFC][PATCH] tcg: allocate memory to spill registers on startup Aurelien Jarno
2009-04-10 14:44 ` Paul Brook
2009-04-10 14:56 ` Aurelien Jarno [this message]
2009-04-10 15:20 ` Paul Brook
2009-04-10 15:31 ` Aurelien Jarno
2009-04-10 15:52 ` Paul Brook
2009-04-10 16:06 ` 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=20090410145609.GA20999@volta.aurel32.net \
--to=aurelien@aurel32.net \
--cc=paul@codesourcery.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).