From: "Blue Swirl" <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Crash due to invalid env->current_tb
Date: Thu, 1 May 2008 19:15:39 +0300 [thread overview]
Message-ID: <f43fc5580805010915r514791e3u1d625e30f275098f@mail.gmail.com> (raw)
In-Reply-To: <200805011704.43953.paul@codesourcery.com>
On 5/1/08, Paul Brook <paul@codesourcery.com> wrote:
> > > T0 = gen_func();
>
> > >
> > > For 64bit target T0 is 64bits so "=a" does not work and "=A" is needed.
> > > The strange thing is that I need to throw away the upper 32bits because
> > > otherwise it won't work. gen_func is defined to return just long but T0
> > > is unsigned long long, this seems inconsistent. The 'and' does not
> > > appear in 32bit targets so it does not harm there.
> >
> > This is because in this special case, T0 is not used as target CPU
> > temporary, but instead to return next TB address. On i386 this is 32
> > bits, so only EAX is needed. TCG does not touch EDX, so it contains
> > garbage. This also means that moving EDX to high word of T0 and then
> > throwing the high word away may be slightly wasteful.
>
>
> Do we need to use T0 at all here? Can't we just use a normal local variable?
I suspect T0 was used to gain extra performance, but in case of 64-bit
target on 32-bit host there is this unnecessary work.
But does cpu-exec.c need to know about T0/T1/T2 at all? Can we replace
exec.h include with cpu.h one?
next prev parent reply other threads:[~2008-05-01 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 11:56 [Qemu-devel] Crash due to invalid env->current_tb Adam Lackorzynski
2008-04-29 17:09 ` Blue Swirl
2008-04-29 18:40 ` Adam Lackorzynski
2008-04-30 9:08 ` Alexander Graf
2008-04-30 15:11 ` Adam Lackorzynski
2008-04-30 15:21 ` Adam Lackorzynski
2008-04-30 17:09 ` Blue Swirl
2008-04-30 17:30 ` Alexander Graf
2008-04-30 18:21 ` Blue Swirl
2008-05-01 12:02 ` Adam Lackorzynski
2008-05-01 15:02 ` Blue Swirl
2008-05-01 16:04 ` Paul Brook
2008-05-01 16:15 ` Blue Swirl [this message]
2008-05-01 16:31 ` Paul Brook
2008-05-02 15:41 ` Adam Lackorzynski
2008-05-03 18:00 ` Blue Swirl
2008-05-03 22:02 ` Paul Brook
2008-04-30 15:28 ` Laurent Vivier
2008-04-30 20:36 ` Adam Lackorzynski
2008-05-02 1:39 ` Bernhard Kauer
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=f43fc5580805010915r514791e3u1d625e30f275098f@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).