From: Glauber Costa <glommer@gmail.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] TCG/GCC breakage
Date: Wed, 11 Mar 2009 00:40:20 -0300 [thread overview]
Message-ID: <5d6222a80903102040reef9775s8aaf9975e7594133@mail.gmail.com> (raw)
I'm seeing a strange behaviour here using qemu-system-x86_64
(kvm not even compiled in) on an i386 host
I'm suspecting gcc is doing something nasty in here, but I'll open it
up here to see if any
of you have any suggestion.
I get segfaults very early in execution, and after some investigation,
I figured out that
ebp register is corrupted. I can't determine where the corruption starts.
I then did rm x86-64-softmmu/op_helper.o; make CC=gcc34, so only this
file get compiled
by an older gcc, and it worked again.
So it seems to me gcc may be generating gibberish somewhere in
helpers, but since
this code is a bit fragile, it might well be some mistake on our part.
Ideas on how to attack it ?
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next reply other threads:[~2009-03-11 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 3:40 Glauber Costa [this message]
2009-03-11 8:32 ` [Qemu-devel] TCG/GCC breakage Aurelien Jarno
2009-03-11 10:34 ` Paul Bolle
2009-03-16 8:26 ` Aurelien Jarno
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=5d6222a80903102040reef9775s8aaf9975e7594133@mail.gmail.com \
--to=glommer@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).