From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 702885 <702885@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 702885] Re: "Internal resource leak" error with ARM NEON vmull.s32 insn
Date: Wed, 19 Jan 2011 13:16:21 +0000 [thread overview]
Message-ID: <AANLkTimWWDdn9nxCvg-+CPX8PmaAHQ4UAJRppcyuQLv9@mail.gmail.com> (raw)
In-Reply-To: <20110119124215.32413.13091.malone@wampee.canonical.com>
On 19 January 2011 12:42, Wolfgang Schildbach <702885@bugs.launchpad.net> wrote:
> This bug is fixed on HEAD in the qemu-meego tree (commit 8493a687d54e542ac4eec8b2f8326415edf37ec4
> A)
Note that the qemu-meego tree disables these warnings using
an #ifdef, so even if the message is not printed we might still
not be handling the temporaries correctly (although there are a
lot of fixes for mishandled temps in that tree).
-- PMM
next prev parent reply other threads:[~2011-01-19 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 14:21 [Qemu-devel] [Bug 702885] [NEW] "Internal resource leak" error with ARM NEON vmull.s32 insn Wolfgang Schildbach
2011-01-19 12:42 ` [Qemu-devel] [Bug 702885] " Wolfgang Schildbach
2011-01-19 13:16 ` Peter Maydell [this message]
2011-01-19 14:28 ` [Qemu-devel] [Bug 702885] Re: "Internal resource leak" error withARM " Schildbach, Wolfgang
2011-01-21 14:36 ` [Qemu-devel] [Bug 702885] Re: "Internal resource leak" error with ARM " Wolfgang Schildbach
2011-01-21 16:01 ` Peter Maydell
2011-01-21 17:17 ` [Qemu-devel] RE: [Bug 702885] Re: "Internal resource leak" error with ARM NEONvmull.s32 insn Wolfgang Schildbach
2011-01-26 13:59 ` [Qemu-devel] [Bug 702885] Re: "Internal resource leak" error with ARM NEON vmull.s32 insn Aurelien Jarno
2011-01-27 4:13 ` Wolfgang Schildbach
2011-02-20 17:17 ` Aurelien Jarno
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=AANLkTimWWDdn9nxCvg-+CPX8PmaAHQ4UAJRppcyuQLv9@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=702885@bugs.launchpad.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 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).