From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] SH: Add prefi, icbi, synco
Date: Mon, 20 Oct 2008 17:27:00 +0100 [thread overview]
Message-ID: <200810201727.01042.paul@codesourcery.com> (raw)
In-Reply-To: <20081020130021.GB20548@linux-sh.org>
> > I disagree. This is something that should be done right from the start.
> > Trying to fix it up later is a real pain. Doing fine grained features
> > isn't that hard. MIPS, sparc, arm, ppc, m68k and sparc already do this.
> > IIRC binutils is only complicated because it tried to create a strict
> > hieracy of features, rather than using feature bits.
>
> When we do it does not matter, but it is completely unrelated from this
> patch, in that there are already plenty of instructions that are specific
> to a certain CPU family that we don't perform an illegal instruction
> exception for. Trying to force the prefi/icbi/synco cases to rework all
> of the existing instructions that aren't universal doesn't make a lot of
> sense, as it is a clear incremental change of existing behaviour, rather
> than a situation caused purely by the addition of these new instructions.
The only cpu we currently claim to support is SH4. When adding support for
other cores these should be properly conditionalized. Unconditionally
implementing additional instructions is a regression. I don't consider "we'll
fix this at some undefined point in the future" to be a good enough answer.
Paul
next prev parent reply other threads:[~2008-10-20 16:27 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 [this message]
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
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=200810201727.01042.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=vladimir@codesourcery.com \
/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).