From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Sat, 23 Apr 2005 12:33:37 +0100 [thread overview]
Message-ID: <200504231233.38717.paul@codesourcery.com> (raw)
In-Reply-To: <20050423110513.423af760@smirftschs.home.tld>
On Saturday 23 April 2005 10:05, developer@isl-gbr.de wrote:
> does this mean this problem is currently not fixable (and maybe "never" -
> in a considerable amount of time will ?)
Correct. It may be fixable, but there's basically zero interest in fixing it.
Qemu is pretty much the only place where this particular behaviour (a single
ret at the end of the code) is required or even desirable. In fact the
opposite is usually true - you want the fast path to be as short as possible
for better cache locality.
IMHO the way forward long-term is to implement some sort of code generation in
qemu. By this I mean incorporating some sort of compiler backend/optimizing
assembler into qemu, not just writing op.c in assembly. Obviously this is a
large chunk of work.
Paul
next prev parent reply other threads:[~2005-04-23 11:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 14:34 [Qemu-devel] X86_64 (AMD64) build segfaults developer
2005-04-21 14:42 ` Paul Brook
2005-04-21 14:59 ` developer
2005-04-21 15:01 ` Paul Brook
2005-04-21 16:02 ` developer
2005-04-22 14:50 ` developer
2005-04-22 15:01 ` Jonas Maebe
2005-04-22 15:41 ` developer
2005-04-22 16:12 ` Jonas Maebe
2005-04-22 16:30 ` developer
2005-04-22 16:33 ` Paul Brook
2005-04-23 9:05 ` developer
2005-04-23 11:33 ` Paul Brook [this message]
2006-03-15 8:15 ` [Qemu-devel] Dynamic compiler future (was Re: X86_64 (AMD64) build segfaults) Antti P Miettinen
2005-04-22 22:12 ` [Qemu-devel] X86_64 (AMD64) build segfaults Joshua Root
2005-04-21 15:11 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2005-04-22 16:35 Jung-uk Kim
2005-04-22 16:49 Jung-uk Kim
2005-04-23 9:06 ` developer
2005-05-02 17:40 ` Jung-uk Kim
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=200504231233.38717.paul@codesourcery.com \
--to=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).