qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: amateur <tianlei.zhao@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Latest git version failed to run 403.gcc benchmark in SPEC CPU2006
Date: Sat, 31 Jul 2010 09:21:42 +0800	[thread overview]
Message-ID: <20100731012142.GA2800@localdomain> (raw)
In-Reply-To: <AANLkTikvyiOrYXDJ5_LcakfZ8KqMxtkoTgi9kgaKXE59@mail.gmail.com>

On Fri. 2010-07-30 14:21:42 +0000, Blue Swirl wrote:
> On Thu, Jul 29, 2010 at 3:40 PM, amateur <tianlei.zhao@gmail.com> wrote:
> > Hi, All
> There's '-d in_asm,op,out_asm' but it may not help much.

Since the program runs a while before fail, that counts a lot of
instructions(hundreds of millions). With this volume of instructions
to trace, the log file would be two large. Anyway, thanks for the
suggestion.

> Once I singlestepped a program under GDB, simultaneously both in
> native host and in QEMU. After each step, both GDBs calculated and
> displayed a XOR checksum from all registers. I had to do some hacks to
> make address layout and register values match in QEMU.

This sounds feasible. I've managed to make the address layout match
for guest program running in qemu and in Simics. I'll try it.

> > 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?
> 
> You may need to use sparc64-linux-gdb.

Tried both sparc64-linux-gdb and sparc-linux-gdb, same result.

      reply	other threads:[~2010-07-31  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 15:40 [Qemu-devel] Latest git version failed to run 403.gcc benchmark in SPEC CPU2006 amateur
2010-07-29 20:20 ` Artyom Tarasenko
2010-07-30 10:50   ` amateur
2010-07-30 14:17     ` Vince Weaver
2010-07-30 14:21 ` Blue Swirl
2010-07-31  1:21   ` amateur [this message]

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=20100731012142.GA2800@localdomain \
    --to=tianlei.zhao@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).