From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ld2.acq - sign extension?
Date: Mon, 19 May 2008 12:51:28 +0000 [thread overview]
Message-ID: <yq0od72ihin.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <yq0wslqiqyp.fsf@jaguar.mkp.net>
>>>>> "Avi" = Avi Kivity <avi@qumranet.com> writes:
Avi> Jes Sorensen wrote:
Avi> r17 is used later on, so your patch makes it uninitialized (if I
Avi> may venture to comment about an assembly language I know nothing
Avi> about).
Oh, on ia64 the sequence is [dest] = [src] so the register usage is
covered I believe.
Avi> Maybe a bug in the instruction emulator?
Yeah it smells like it, that or in QEMU. I am not quite sure who is
responsible for this part. Does QEMU just provide registers somewhere
else and the instruction emulation reads them out of the QEMU share
space, or is there some other magic going on?
Cheers,
Jes
next prev parent reply other threads:[~2008-05-19 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 9:27 ld2.acq - sign extension? Jes Sorensen
2008-05-19 9:46 ` Andreas Schwab
2008-05-19 9:55 ` Jes Sorensen
2008-05-19 10:31 ` Avi Kivity
2008-05-19 12:12 ` Matthew Chapman
2008-05-19 12:25 ` Jes Sorensen
2008-05-19 12:51 ` Jes Sorensen [this message]
2008-05-20 4:48 ` Xu, Anthony
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=yq0od72ihin.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-ia64@vger.kernel.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