All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: John Reiser <jreiser@bitwagon.com>
Subject: Re: [Qemu-devel] bug: qemu-0.9.0 emulating mipsel (32-bit R3000) on amd64
Date: Mon, 7 May 2007 16:46:52 +0100	[thread overview]
Message-ID: <200705071646.54894.paul@codesourcery.com> (raw)
In-Reply-To: <20070507121310.GA18535@caradoc.them.org>

On Monday 07 May 2007, Daniel Jacobowitz wrote:
> On Sun, May 06, 2007 at 09:04:52PM +0100, Thiemo Seufer wrote:
> > This looks like another instance of "Qemu/MIPS doesn't handle
> > self-modifying code correctly" (the break instructions inserted
> > by gdb are exactly this).
> >
> > A gross workaround is
> > http://lists.nongnu.org/archive/html/qemu-devel/2007-05/msg00037.html
>
> Someone might want to try:
>   http://lists.nongnu.org/archive/html/qemu-devel/2007-04/msg00514.html

I think breakpoints and FPU are separate bugs.

I notice that the FPU enable bit (CP0C1_FP) is not included in the TB flags. 
My guess is you need to modify exec.c:tb_find_fast to include this.

Paul

  reply	other threads:[~2007-05-07 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 18:45 [Qemu-devel] bug: qemu-0.9.0 emulating mipsel (32-bit R3000) on amd64 John Reiser
2007-05-06 20:04 ` Thiemo Seufer
2007-05-06 20:07   ` Thiemo Seufer
2007-05-07 12:13   ` Daniel Jacobowitz
2007-05-07 15:46     ` Paul Brook [this message]
2007-05-07 22:46     ` [Qemu-devel] workaround: " John Reiser
2007-05-07 23:03       ` Paul Brook
2007-05-07 23:08         ` Paul Brook
2007-05-08 18:03     ` [Qemu-devel] bug: " Stefan Weil
2007-05-08 23:50   ` John Reiser
2007-05-09  1:04     ` Thiemo Seufer

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=200705071646.54894.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=jreiser@bitwagon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.