From: Richard Henderson <rth@twiddle.net>
To: Stuart Brady <sdb@zubnet.me.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] tcg-hppa: Finish the port.
Date: Wed, 17 Mar 2010 07:56:12 -0700 [thread overview]
Message-ID: <4BA0ED8C.8000404@twiddle.net> (raw)
In-Reply-To: <20100317015829.GC23195@zubnet.me.uk>
On 03/16/2010 06:58 PM, Stuart Brady wrote:
> The tcg_reg_free() calls worry me slightly, but I assume they're safe...
Yeah, that one's rather gross.
Since Aurelien's generic div/rem patch I could simply remove all
that millicode stuff, including that tcg_reg_free, and let the
generic code handle this instead. Which would get to the same
millicode routine via one or two extra levels of indirection.
Thoughts?
r~
next prev parent reply other threads:[~2010-03-17 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 15:50 [Qemu-devel] [PATCH 0/4] tcg-hppa get it working, v2.1 Richard Henderson
2010-03-12 14:58 ` [Qemu-devel] [PATCH 4/4] tcg-hppa: Compute is_write in cpu_signal_handler Richard Henderson
2010-03-17 2:10 ` Stuart Brady
2010-03-17 2:23 ` Stuart Brady
2010-03-17 14:49 ` Richard Henderson
2010-03-16 15:52 ` [Qemu-devel] [PATCH 1/4] tcg-hppa: Fix const errors in hppa-dis.c Richard Henderson
2010-03-17 1:46 ` Stuart Brady
2010-03-23 21:26 ` Aurelien Jarno
2010-03-16 15:52 ` [Qemu-devel] [PATCH 2/4] tcg-hppa: Fix 64-bit argument ordering Richard Henderson
2010-03-17 1:49 ` Stuart Brady
2010-03-23 21:27 ` Aurelien Jarno
2010-03-16 15:53 ` [Qemu-devel] [PATCH 3/4] tcg-hppa: Finish the port Richard Henderson
2010-03-17 1:58 ` Stuart Brady
2010-03-17 14:56 ` Richard Henderson [this message]
2010-03-17 17:04 ` Richard Henderson
2010-03-17 20:01 ` Stuart Brady
2010-03-23 21:28 ` Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 15:45 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=4BA0ED8C.8000404@twiddle.net \
--to=rth@twiddle.net \
--cc=qemu-devel@nongnu.org \
--cc=sdb@zubnet.me.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.