From: "developer@isl-gbr.de" <developer@isl-gbr.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Fri, 22 Apr 2005 17:41:31 +0200 [thread overview]
Message-ID: <20050422174131.779509e3@smirftschs.home.tld> (raw)
In-Reply-To: <1e4ee963664f770c5ba5890f3e66e469@elis.ugent.be>
Hello Jonas, here is the output of the command you gave me for this function, does this help ?
0000000000001ab0 <op_bsfw_T0_cc>:
1ab0: 89 d8 mov %ebx,%eax
1ab2: 25 ff ff 00 00 and $0xffff,%eax
1ab7: 75 27 jne 1ae0 <op_bsfw_T0_cc+0x30>
1ab9: eb 19 jmp 1ad4 <op_bsfw_T0_cc+0x24>
1abb: 31 d2 xor %edx,%edx
1abd: 66 data16
1abe: 66 data16
1abf: 90 nop
1ac0: d1 f8 sar %eax
1ac2: ff c2 inc %edx
1ac4: a8 01 test $0x1,%al
1ac6: 74 f8 je 1ac0 <op_bsfw_T0_cc+0x10>
1ac8: 41 89 d4 mov %edx,%r12d
1acb: c7 45 2c 01 00 00 00 movl $0x1,0x2c(%rbp)
1ad2: eb 07 jmp 1adb <op_bsfw_T0_cc+0x2b>
1ad4: c7 45 2c 00 00 00 00 movl $0x0,0x2c(%rbp)
1adb: c3 retq
1adc: 66 data16
1add: 66 data16
1ade: 66 data16
1adf: 90 nop
1ae0: 31 d2 xor %edx,%edx
1ae2: a8 01 test $0x1,%al
1ae4: 75 e2 jne 1ac8 <op_bsfw_T0_cc+0x18>
1ae6: eb d3 jmp 1abb <op_bsfw_T0_cc+0xb>
1ae8: 66 data16
1ae9: 66 data16
1aea: 66 data16
1aeb: 90 nop
1aec: 66 data16
1aed: 66 data16
1aee: 66 data16
1aef: 90 nop
On Fri, 22 Apr 2005 17:01:27 +0200
Jonas Maebe <jonas.maebe@elis.ugent.be> wrote:
>
> 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
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2005-04-22 15:56 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 [this message]
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=20050422174131.779509e3@smirftschs.home.tld \
--to=developer@isl-gbr.de \
--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).