From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Kaz Kylheku <kaz@zeugmasystems.com>, linux-mips@linux-mips.org
Subject: Re: SiByte 1480 & Branch Likely instructions?
Date: Mon, 10 Dec 2007 15:35:23 +0000 [thread overview]
Message-ID: <20071210153523.GA19384@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0712101522100.1177@blysk.ds.pg.gda.pl>
On Mon, Dec 10, 2007 at 03:28:52PM +0000, Maciej W. Rozycki wrote:
> > > Not really a kernel-related question. I've discovered that GCC 4.1.1
> > > (which I'm not using for kernel compiling, but user space) generates
> > > branch likely instructions by default, even though the documentation
> > > says that their use is off by default for MIPS32 and MIPS64, because
> > > they are considered deprecated. They are documented as obsolete for the
> > > Broadcom chips I am working with.
> >
> > Microarchitecture guys love to hate branch likely. But the deprecation is
> > a dream. Binary compatibility will always require those instructions to
> > continue to exist so the genie is out of the bottle and so I feel very
> > certain to predict that a future MIPS 3 specification will contain branch
> > likely.
>
> We have been there before -- binary compatibility does not preclude
> emulation. And I do not mean keeping the MIPS I toys (as they might be
> seen these days) running, but serious products deployed commercially, like
> newer VAX implementations that kept full binary compatibility with their
> predecessors in the area of the some of the more arcane instructions only
> by means of emulating them in the OS.
It would devastate the performance of some binaries.
As an intellectual challenge, how far can you strip down a MIPS
implementation and emulate removed instructions in the kernel ;-)
Ralf
next prev parent reply other threads:[~2007-12-10 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 21:54 SiByte 1480 & Branch Likely instructions? Kaz Kylheku
2007-12-07 21:54 ` Kaz Kylheku
2007-12-07 23:39 ` Kaz Kylheku
2007-12-07 23:39 ` Kaz Kylheku
2007-12-09 5:26 ` Ralf Baechle
2007-12-14 3:05 ` GCC bug affecting MIPS (was Re: SiByte 1480 & Branch Likely instructions?) Kaz Kylheku
2007-12-14 3:05 ` Kaz Kylheku
2007-12-09 5:14 ` SiByte 1480 & Branch Likely instructions? Ralf Baechle
2007-12-10 15:28 ` Maciej W. Rozycki
2007-12-10 15:35 ` Ralf Baechle [this message]
2007-12-10 16:20 ` Maciej W. Rozycki
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=20071210153523.GA19384@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kaz@zeugmasystems.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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