All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin <akuster@kama-aina.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM TCG conversion
Date: Mon, 31 Mar 2008 08:54:11 -1000	[thread overview]
Message-ID: <47F13353.3080504@kama-aina.net> (raw)
In-Reply-To: <200803310458.53439.paul@codesourcery.com>

Paul Brook wrote:
> I've just checked in a series of patches converting the ARM target to the new 
> TCG code generator.  All the dyngen ops have been removed.  The remaining 
> code is a muxture of explicit and implicit operands, so there's still some 
> cleanup to be done.
> 
> With the exception of fixing a couple of bugs in the SIMD instructions, the 
> code should be functionally identical.
> 
> If you do discover errors, it would be useful if you could track down exactly 
> which patch caused the failure, and preferable a reasonable sized 
> self-contained testcase. The code should still be functional at each of the 
> intermediate points.
> 
> Paul
> 
> 
> 
> 
Paul,

I am seeing two resource leak messages when booting the PXA27x 
mainstone. Not sure if this is the clean up you speak of. No I have not 
looked into which patches might be causing this, maybe I will be able to 
poke around some time this week.. The cvs sources from March 11 worked 
fine. yes, I know.. not very useful.


Uncompressing 
Linux........................................................................................................ 
done, booting the kernel.
Internal resource leak before c002fb08
...

XScale DSP coprocessor detected.
Internal resource leak before c002fb08

  -armin

      reply	other threads:[~2008-03-31 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31  3:58 [Qemu-devel] ARM TCG conversion Paul Brook
2008-03-31 18:54 ` Armin [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=47F13353.3080504@kama-aina.net \
    --to=akuster@kama-aina.net \
    --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.