From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages
Date: Mon, 05 May 2014 20:09:58 -0400 [thread overview]
Message-ID: <53682856.5040005@gentoo.org> (raw)
In-Reply-To: <CAEdQ38FWiYkmV6GUxKsOLKSOZw8EPiSQFR8bkh-z6j2txmu7+g@mail.gmail.com>
On 05/05/2014 19:36, Matt Turner wrote:
> On Mon, May 5, 2014 at 3:02 PM, Joshua Kinard <kumba@gentoo.org> wrote:
>> I cannot speak for anything outside of the standard/original MIPS ISAs, but
>> I thought we killed off mips1 long ago. When did that come back? Almost
>> anything out there should be able to handle mips2 at a bare minimum (only
>> R2000 and R3000-based systems, like certain DECStations, would need mips1).
>> mips2 is also the branch point for the mips32r* ISAs, so if any of the
>> original, 32-bit ISAs should be kept, that would be mips2. mips1 can go.
>
> We've had this discussion before. If you're going to have >mips2
> stages, then there's zero reason to have mips2 stages since mips2
> effectively doesn't exist.
It's been a while, but I thought we only kept a mips2 stage1 around for
those that wanted a baseline to build their own stage2 or stage3's from.
You can do this with a mips1 as well, but mips2 is, more or less, the
baseline from which all other possible ISAs and stages can be built from, as
long as you don't care about R2k or R3k CPUs. stage3's can be the higher
mips32r* ISAs.
I personally don't see a point in having mips1 or mips2 stage3's, only a
stage1 to use as a bootstrap for new machines or ISAs.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2014-05-06 0:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 14:06 [gentoo-mips] Reducing the number of the MIPS supported stages Markos Chandras
2014-05-05 17:04 ` Panagiotis Christopoulos
2014-05-05 17:17 ` Markos Chandras
2014-05-05 17:13 ` Justin Cormack
2014-05-05 17:16 ` Markos Chandras
2014-05-05 17:22 ` Matt Turner
2014-05-05 17:29 ` Markos Chandras
2014-05-05 23:34 ` Matt Turner
2014-05-05 22:02 ` Joshua Kinard
2014-05-05 23:30 ` Matt Turner
2014-05-06 0:15 ` Joshua Kinard
2014-05-05 23:36 ` Matt Turner
2014-05-06 0:09 ` Joshua Kinard [this message]
2014-05-06 7:07 ` Markos Chandras
2014-05-06 8:10 ` Joshua Kinard
2014-05-06 17:50 ` Markos Chandras
2014-05-06 21:37 ` Joshua Kinard
2014-05-07 7:06 ` Markos Chandras
2014-05-07 7:22 ` Joshua Kinard
2014-05-06 11:32 ` Anthony G. Basile
2014-05-06 17:40 ` Markos Chandras
2014-05-05 19:19 ` [gentoo-mips] " Anthony G. Basile
2014-05-05 19:33 ` Markos Chandras
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=53682856.5040005@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-mips@lists.gentoo.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