From: Gerhard Wiesinger <lists@wiesinger.com>
To: Kevin O'Connor <kevin@koconnor.net>, Bernhard Walle <bernhard@bwalle.de>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] uvesafb doesn't work with seabios
Date: Tue, 13 May 2014 20:08:41 +0200 [thread overview]
Message-ID: <53725FA9.6050607@wiesinger.com> (raw)
In-Reply-To: <20140513154115.GA12093@morn.localdomain>
On 13.05.2014 17:41, Kevin O'Connor wrote:
> The x86emu code does not properly emulate "leal" (as near as I can
> tell it treats it as a "leaw" instead), which leads to all sorts of
> bizarre behavior when it tries to interpret the code. This type of
> issue has occurred for a bunch of instructions (on both x86emu and on
> an emulator Windows uses) and we've worked around it in SeaVGABIOS
> with a combination of gcc compiler flags and by post processing gcc's
> assembler to remove some troublesome instructions. Unfortunately, I
> don't know of any way to convince gcc to not emit the "leal"
> instruction and the instruction appears too complex to readily patch
> out of the assembler.
Can't that wrong behaviour of "leal" instruction be fixed in qemu?
Ciao,
Gerhard
next prev parent reply other threads:[~2014-05-13 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:06 [Qemu-devel] uvesafb doesn't work with seabios Bernhard Walle
2014-05-10 15:07 ` Kevin O'Connor
2014-05-11 11:42 ` Bernhard Walle
2014-05-11 12:37 ` Kevin O'Connor
2014-05-11 14:19 ` Bernhard Walle
2014-05-12 5:29 ` Kevin O'Connor
2014-05-12 18:53 ` Bernhard Walle
2014-05-12 20:07 ` Kevin O'Connor
2014-05-13 5:52 ` Bernhard Walle
2014-05-13 9:20 ` Bernhard Walle
2014-05-13 15:41 ` Kevin O'Connor
2014-05-13 18:08 ` Gerhard Wiesinger [this message]
2014-05-13 18:20 ` Kevin O'Connor
2014-05-13 19:48 ` Bernhard Walle
2014-05-14 19:08 ` Bernhard Walle
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=53725FA9.6050607@wiesinger.com \
--to=lists@wiesinger.com \
--cc=bernhard@bwalle.de \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.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).