From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Fri, 22 Apr 2005 17:01:27 +0200 [thread overview]
Message-ID: <1e4ee963664f770c5ba5890f3e66e469@elis.ugent.be> (raw)
In-Reply-To: <20050422165042.6da168de@smirftschs.home.tld>
On 22 apr 2005, at 16:50, developer@isl-gbr.de wrote:
> dyngen: ret or jmp expected at the end of op_bsfw_T0_cc
>
> any ideas for that ? :)
gcc 4.0 apparently performs some sort of optimization which is
incompatible with qemu's object parser. Post the code of that routine
to have people see what the problem is. To get it, do
objdump -d target-i386/op.o |less
search for op_bsfw_T0_cc and post the code of that routine.
Jonas
next prev parent reply other threads:[~2005-04-22 15:11 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 [this message]
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
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=1e4ee963664f770c5ba5890f3e66e469@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--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).