From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] SH: Add prefi, icbi, synco
Date: Mon, 20 Oct 2008 18:19:51 +0100 [thread overview]
Message-ID: <200810201819.51767.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0810201015k42a02241r638eae16e24364bf@mail.gmail.com>
On Monday 20 October 2008, Laurent Desnogues wrote:
> On Mon, Oct 20, 2008 at 12:54 PM, Paul Brook <paul@codesourcery.com> wrote:
> > Doing fine grained features isn't that
> > hard. MIPS, sparc, arm, ppc, m68k and sparc already do this.
>
> So let's say someone finds some unprotected use of some ARM
> instructions, should that be reported and is there any hope the
> patch will ever be considered by the maintainer of the ARM target?
> (Examples are ldrex/strex and ubfx/sbfx.)
Yes.
> Also what about undetected undefined instructions which I asked
> about last May?
>
> http://lists.gnu.org/archive/html/qemu-devel/2008-05/msg00844.html
>
> Given the lack of answer at that time, I thought it didn't matter. I now
> see I was wrong. It's a pity communication is almost impossible.
Rejecting incorrect patches is always easier than verifying that patches are
correct.
Paul
prev parent reply other threads:[~2008-10-20 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:52 [Qemu-devel] [PATCH] SH: Add prefi, icbi, synco Vladimir Prus
2008-10-17 19:56 ` Paul Brook
2008-10-20 4:01 ` Paul Mundt
2008-10-20 10:54 ` Paul Brook
2008-10-20 13:00 ` Paul Mundt
2008-10-20 16:27 ` Paul Brook
2008-10-20 16:31 ` Vladimir Prus
2008-10-20 16:46 ` Paul Brook
2008-10-20 16:49 ` Paul Mundt
2008-10-20 17:07 ` Paul Brook
2008-10-20 17:15 ` Laurent Desnogues
2008-10-20 17:19 ` Paul Brook [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=200810201819.51767.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=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).