From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] A question about ARM target
Date: Fri, 23 May 2008 09:59:04 +0200 [thread overview]
Message-ID: <761ea48b0805230059y5e0dbed8k7a83dbf87aa5c1b8@mail.gmail.com> (raw)
I have been taking a look at ARM target and found some holes
in undefined instructions detection. Is that something we
want correct or not? (Note, I am not talking about
unpredictable encoding, but architecturally undefined
encoding.)
Laurent
reply other threads:[~2008-05-23 7:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=761ea48b0805230059y5e0dbed8k7a83dbf87aa5c1b8@mail.gmail.com \
--to=laurent.desnogues@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).