From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Bugs in ppc TCG backend
Date: Fri, 28 Nov 2008 20:32:31 +0100 [thread overview]
Message-ID: <20081128193231.GA20624@networkno.de> (raw)
Hello All,
since Revision 5729 I see failures with my usual set of mips regression
tests. The breakage is limited to the ppc TCG backend, apparently r5729
triggers bugs there.
The problem should be reproducible when attempting to install Debian
mipsel. The symptom is a segfault of qemu-system-mipsel after selecting
the country. For qemu-system-mips64el, the segfault happens much
earlier after only a few instructions.
I think I found one alignment bug, applying the appended patch moves
the crash in qemu-system-mips64el to a later point.
Thiemo
Index: qemu-work/tcg/tcg.c
===================================================================
--- qemu-work.orig/tcg/tcg.c 2008-11-27 19:47:42.000000000 +0100
+++ qemu-work/tcg/tcg.c 2008-11-28 19:24:42.000000000 +0100
@@ -621,7 +621,7 @@
#endif
#ifdef TCG_TARGET_CALL_ALIGN_ARGS
/* some targets want aligned 64 bit args */
- if (i & 1) {
+ if ((i & 1) && !(sizemask & (2 << (i - 1)))) {
*gen_opparam_ptr++ = TCG_CALL_DUMMY_ARG;
}
#endif
reply other threads:[~2008-11-28 19:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081128193231.GA20624@networkno.de \
--to=ths@networkno.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).