From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP)
Date: Wed, 28 Aug 2013 07:31:59 -0700 [thread overview]
Message-ID: <521E09DF.20102@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8uJGphig_gzc2hrJCHejjq1qW-eq7NXScDHWVRRk7KeA@mail.gmail.com>
On 08/28/2013 01:15 AM, Peter Maydell wrote:
> [*] not impossible, we already do something on the ppc
> that's similar; however I'd really want to take the time to
> figure out how to do endianness swapping "properly"
> and what qemu does currently before messing with it.
I've got a loose plan in my head for how to clean up handling of
reverse-endian load/store instructions at both the translator and
tcg backend levels.
Hopefully it make the ppc, sparc, and s390 targets cleaner.
I would think that would equally apply to the arm setend.
r~
WARNING: multiple messages have this Message-ID (diff)
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP)
Date: Wed, 28 Aug 2013 07:31:59 -0700 [thread overview]
Message-ID: <521E09DF.20102@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8uJGphig_gzc2hrJCHejjq1qW-eq7NXScDHWVRRk7KeA@mail.gmail.com>
On 08/28/2013 01:15 AM, Peter Maydell wrote:
> [*] not impossible, we already do something on the ppc
> that's similar; however I'd really want to take the time to
> figure out how to do endianness swapping "properly"
> and what qemu does currently before messing with it.
I've got a loose plan in my head for how to clean up handling of
reverse-endian load/store instructions at both the translator and
tcg backend levels.
Hopefully it make the ppc, sparc, and s390 targets cleaner.
I would think that would equally apply to the arm setend.
r~
next prev parent reply other threads:[~2013-08-28 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:39 [Qemu-trivial] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP) Stefan Weil
2013-08-28 4:39 ` [Qemu-devel] " Stefan Weil
2013-08-28 8:15 ` [Qemu-trivial] " Peter Maydell
2013-08-28 8:15 ` [Qemu-devel] " Peter Maydell
2013-08-28 14:31 ` Richard Henderson [this message]
2013-08-28 14:31 ` Richard Henderson
2013-08-28 14:34 ` [Qemu-trivial] " Peter Maydell
2013-08-28 14:34 ` Peter Maydell
2013-08-28 15:26 ` [Qemu-devel] [RFC] Streamlining endian handling in TCG Richard Henderson
2013-08-28 16:38 ` Peter Maydell
2013-08-28 17:16 ` Richard Henderson
2013-08-28 17:28 ` Peter Maydell
2013-08-28 17:45 ` Richard Henderson
2013-08-28 17:41 ` Stefan Weil
2013-08-28 20:42 ` Edgar E. Iglesias
2013-08-28 21:06 ` Peter Maydell
2013-08-28 21:23 ` Richard Henderson
2013-09-02 23:42 ` Aurelien Jarno
2013-09-03 15:11 ` Richard Henderson
2013-09-01 15:35 ` [Qemu-trivial] [PATCH] target-arm: Report unimplemented opcodes (LOG_UNIMP) Michael Tokarev
2013-09-01 15:35 ` [Qemu-devel] " Michael Tokarev
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=521E09DF.20102@twiddle.net \
--to=rth@twiddle.net \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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.