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 18:02:38 -0400 [thread overview]
Message-ID: <53680A7E.9000209@gentoo.org> (raw)
In-Reply-To: <CAEdQ38FXwAdL-61br_haW-XvGP2Zv9+Q4L2qzQ1fykM7kOfftw@mail.gmail.com>
On 05/05/2014 13:22, Matt Turner wrote:
> On Mon, May 5, 2014 at 7:06 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
>> Hi all,
>>
>> Right now the number of stages for each endianness is 8:
>>
>> - mips1
>> - mips32
>> - mips32r2
>
> Do we need r1 and r2 stages?
>
> (Isn't r3 a thing now?)
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.
>> - mips3
>> - mips4
>> - mips4_r10
>
> Big endian only.
>
Seconded. We still support SGI systems, which max out at the mips4 ISA. If
we drop support for mips3, that will cut off any R4x00-based Indigo2 and
Indy systems, but I believe those to be fairly rare anyways (and the R4600
still has quirks about it that can pose challenges).
mips4 little-endian is only useful for the old Cobalt RaQ2 and Qube
hardware, which I don't think is reasonable anymore. Modern gcc takes long
enough on an SGI system with a secondary cache -- the Cobalt's low-powered
RM5231 with no L2 would make 4.8 or 4.9 even more excruciating. Max memory
there is 256MB of RAM, and I don't know if gcc-4.9 will build under that.
And I don't see a point in doing an R10K-specific mips4 build. The standard
mips4 build is good enough, and users of R10K systems can rebuild to gain
the R10K enhancements if needed.
So, keep mips4 big-endian as a standard stage build, let's do a mips3
big-endian build maybe once or twice a year, and drop mips4 little-endian
and R10K mips4.
--
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-05 22:02 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 [this message]
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
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=53680A7E.9000209@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