qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bob Deblier <bob.deblier@telenet.be>
To: Karl Magdsick <kmagnum@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu crashes and freezes on x86_64/amd64 host
Date: Sat, 09 Oct 2004 07:29:53 +0200	[thread overview]
Message-ID: <1097299793.2834.18.camel@orion> (raw)
In-Reply-To: <cd8ecdef04100817224ea0b06c@mail.gmail.com>

On Sat, 2004-10-09 at 02:22, Karl Magdsick wrote:
> What is your compiler target when creating the qemu executible?

Native, i.e. x86_64-linux-gnu.

> My understanding is that almost all of the instructions in 64-bit mode
> are reverse-compatible with 32-bit mode, but a few have changed
> slightly.  If your qemu executible is compiled for 64-bit mode (and is
> therefore being run in 64-bit usermode), but the jit is generating
> 32-bit code, this could be problematic for a small number of
> instructions.  I have no direct knowledge of the differences between
> the instruction encodings for 32-bit and 64-bit modes, just hearsay.
> 
> Just a guess.

>From looking at the code, I don't get the impression that that's the
case. It may just be that some of the code isn't 64-bit clean, i.e. that
there are places where the coders have assumed that sizeof(pointer) = 4,
etc.

More investigating *sigh*

Bob

  reply	other threads:[~2004-10-09  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 18:54 [Qemu-devel] qemu crashes and freezes on x86_64/amd64 host Bob Deblier
2004-10-09  0:22 ` Karl Magdsick
2004-10-09  5:29   ` Bob Deblier [this message]
2004-10-09 10:08     ` Johannes Schindelin
2004-10-09 12:03       ` Bob Deblier
2004-10-09 14:06         ` Johannes Schindelin
2004-10-09 15:28           ` Bob Deblier
2004-10-09 16:19   ` [Qemu-devel] " Andi Kleen
2004-10-09 18:31     ` Karl Magdsick
2004-10-09 18:38       ` Andi Kleen

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=1097299793.2834.18.camel@orion \
    --to=bob.deblier@telenet.be \
    --cc=kmagnum@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).