From: Richard Henderson <rth@twiddle.net>
To: identifier scorpio <cidentifier@yahoo.com.cn>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Porting TCG to alpha platform
Date: Fri, 29 Jan 2010 09:04:58 -0800 [thread overview]
Message-ID: <4B63153A.6070509@twiddle.net> (raw)
In-Reply-To: <62332.72612.qm@web15907.mail.cnb.yahoo.com>
On 01/28/2010 05:55 PM, identifier scorpio wrote:
> 1. adding constraints for operation mov_i32/movi_i32/mov_i64/movi_i64
> 2. replacing "goto do_arith" with "break" for INDEX_op_not_i32/i64 case
> handling in tcg_out_op
Oops.
> 3. removing the redundant declaration for "alpha_tb_set_jmp_target()" at
> tail of tcg-target.c, it has been declared in exec-all.h
Ah, yes, a line I had to add temporarily for the x86 compiler; I meant
to take it out again.
> I just find that a suspect bug in tcg_out_brcond() and have not tried yet.
>
> if ( opc == 0) {
> opc = cmp_opc[cond];
> if ( const_arg2) { /* should be if (const_arg2 && arg2 & ~0xff == 0) ?
> tcg_out_fmt_opi(s, opc, ...)
{ INDEX_op_brcond_i32, { "rJ", "rI" } },
{ INDEX_op_brcond_i64, { "rJ", "rI" } },
The "I" constraint is supposed to have already limited the constant to 0
.. 0xff. You could put an assert there if you like, to make sure
everything is going as it should.
> Your code is more skilled and I learn a lot from it, but I haven't yet
> recognized the key difference between your version and mine. In last
> mail, you've said that "Mainly, tcg_target_long was used places that
> could be holding HOST values, which means that the host values would
> have been truncated to 32 bits.", and I can't fully understand it, may
> you put it more clearly.
It was a mis-statement made while tired. Of course tcg_target_long is
defined to int64_t when TCG_TARGET_REG_BITS == 64, so there was no
truncation to 32 bits.
Have you tested of any of the other embedded targets? You may be able
to find the error with one of those easier than finding it emulating
full-scale Windows. See the images at the bottom of the QEMU download page.
r~
next prev parent reply other threads:[~2010-01-29 17:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 15:47 [Qemu-devel] [PATCH] Porting TCG to alpha platform identifier scorpio
2010-01-22 18:00 ` Richard Henderson
2010-01-26 1:19 ` Richard Henderson
2010-01-29 1:55 ` identifier scorpio
2010-01-29 17:04 ` Richard Henderson [this message]
2010-01-29 21:38 ` Edgar E. Iglesias
2010-01-29 23:04 ` Stefan Weil
2010-01-30 0:38 ` Edgar E. Iglesias
2010-01-30 1:14 ` Laurent Desnogues
2010-01-30 9:30 ` [Qemu-devel] [BUG] qemu-x86_64 crash when running bntest (was: [PATCH] Porting TCG to alpha platform) Stefan Weil
2010-01-30 9:59 ` Laurent Desnogues
2010-01-30 14:47 ` Laurent Desnogues
2010-01-29 17:37 ` [Qemu-devel] [PATCH] Porting TCG to alpha platform Richard Henderson
2010-01-29 19:19 ` Richard Henderson
2010-01-30 2:45 ` identifier scorpio
2010-01-31 23:09 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2010-01-21 3:42 identifier scorpio
2010-01-21 18:18 ` Stefan Weil
2010-01-20 17:19 identifier scorpio
2010-01-20 21:26 ` Richard Henderson
2010-01-19 8:47 identifier scorpio
2010-01-19 20:18 ` Richard Henderson
2010-01-19 21:35 ` malc
2010-01-19 21:42 ` Stefan Weil
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=4B63153A.6070509@twiddle.net \
--to=rth@twiddle.net \
--cc=cidentifier@yahoo.com.cn \
--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).