From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] and now bus error for i386 guest
Date: Wed, 5 Dec 2007 23:36:42 +0200 [thread overview]
Message-ID: <f43fc5580712051336q610aae74xecdd3a0a68f1ede3@mail.gmail.com> (raw)
In-Reply-To: <4756B6C9.3080507@shaddybaddah.name>
On 12/5/07, Shaddy Baddah <shaddy.baddah@shaddybaddah.name> wrote:
> 0x1e958 <main+13992>: ld [ %l6 + 0x8c ], %l1
> 0x1e95c <main+13996>: call 0xa90b4 <cpu_x86_exec>
> 0x1e960 <main+14000>: mov %l1, %o0
Maybe you missed the effect of the delay slot. The first argument is
prepared in %l1 and moved to %o0 in the delay slot of the call
instruction.
> 0x240a4 <main_loop+152>: sethi %hi(0x258800), %g4
> 0x240a8 <main_loop+156>: or %g4, 0x4c, %g4 ! 0x25884c
> 0x240ac <main_loop+160>: ld [ %g4 ], %g4
> 0x240b0 <main_loop+164>: st %g4, [ %fp + -20 ]
> 0x240b4 <main_loop+168>: ld [ %fp + -20 ], %o0
> 0x240b8 <main_loop+172>: call 0x14fa64 <cpu_x86_exec>
> 0x240bc <main_loop+176>: nop
This looks like equivalent code, only dumber version using an
intermediate store and not using the delay slot.
next prev parent reply other threads:[~2007-12-05 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 7:04 [Qemu-devel] Alpha build failure: dyngen picking out a nameless symbol Shaddy Baddah
2007-11-14 8:10 ` [Qemu-devel] now ppc build failure: dyngen: empty code for op_splatw_T1_64 Shaddy Baddah
2007-11-14 13:13 ` [Qemu-devel] and now bus error for i386 guest Shaddy Baddah
2007-11-14 20:42 ` Blue Swirl
2007-12-04 4:21 ` Shaddy Baddah
2007-12-04 13:23 ` Shaddy Baddah
2007-12-04 18:54 ` Blue Swirl
2007-12-05 14:33 ` Shaddy Baddah
2007-12-05 21:36 ` Blue Swirl [this message]
2007-12-06 0:17 ` Shaddy Baddah
2007-12-06 9:10 ` Blue Swirl
2007-12-06 15:19 ` Blue Swirl
2007-11-15 20:01 ` [Qemu-devel] Alpha build failure: dyngen picking out a nameless symbol Blue Swirl
2007-11-15 22:50 ` Paul Brook
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=f43fc5580712051336q610aae74xecdd3a0a68f1ede3@mail.gmail.com \
--to=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).