From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=44122 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OeVDt-0000er-Hy for qemu-devel@nongnu.org; Thu, 29 Jul 2010 11:40:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OeVDp-0001eY-1g for qemu-devel@nongnu.org; Thu, 29 Jul 2010 11:40:40 -0400 Received: from mail-pv0-f173.google.com ([74.125.83.173]:64864) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OeVDo-0001dj-Lh for qemu-devel@nongnu.org; Thu, 29 Jul 2010 11:40:36 -0400 Received: by pvg7 with SMTP id 7so158063pvg.4 for ; Thu, 29 Jul 2010 08:40:35 -0700 (PDT) Date: Thu, 29 Jul 2010 23:40:25 +0800 From: amateur Message-ID: <20100729154025.GB3422@localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] Latest git version failed to run 403.gcc benchmark in SPEC CPU2006 Reply-To: amateur List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, All I'm trying to run benchmarks from SPEC CPU2006 compiled for SPARC on top of qemu-sparc32plus. However, several benchmarks failed to get the correct result. One of the failed benchmarks, 403.gcc, runs for a while and then print an error message and exit. However, the same compiled gcc binary for SPARC runs quite well in Simics(a commercial emulator) and give the correct result. So I think there may be a bug in Qemu. Has anyone meet the same kind of problem before? I can do some debug, but I have no clue on how to do it. Could anyone please give me some hint on this? I have read the source code, but find it really hard to track down guest program miss-behavior problem. BTW, when I use sparc-linux-gdb with qemu-sparc32plus, it connect, but give the wrong value when print local variables. So, I'm really lost. Can anyone confirm on this, or I'm doing it the wrong way? -- As of next Tuesday, C will be flushed in favor of COBOL. Please update your programs.