From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 349091381FA for ; Tue, 6 May 2014 11:32:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1023CE0B05; Tue, 6 May 2014 11:32:30 +0000 (UTC) Received: from virtual.dyc.edu (mail.virtual.dyc.edu [67.222.116.22]) by pigeon.gentoo.org (Postfix) with ESMTP id 9B48AE0B05 for ; Tue, 6 May 2014 11:32:29 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-145-97.buffalo.res.rr.com [74.77.145.97]) by virtual.dyc.edu (Postfix) with ESMTPSA id 814477E00EA for ; Tue, 6 May 2014 07:32:28 -0400 (EDT) Message-ID: <5368C856.3010602@opensource.dyc.edu> Date: Tue, 06 May 2014 07:32:38 -0400 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@lists.gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 To: gentoo-mips@lists.gentoo.org Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages References: <53679ACC.3000809@gentoo.org> <53680A7E.9000209@gentoo.org> <53682856.5040005@gentoo.org> <53688A17.2070509@gentoo.org> In-Reply-To: <53688A17.2070509@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: c2b6c5ab-9679-45dd-a19e-408f6090ad1c X-Archives-Hash: 76732d557567b925ed5d03fd79e657e2 On 05/06/2014 03:07 AM, Markos Chandras wrote: > On 05/06/2014 01:09 AM, Joshua Kinard wrote: >> On 05/05/2014 19:36, Matt Turner wrote: >>> On Mon, May 5, 2014 at 3:02 PM, Joshua Kinard 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. >> > > (picking up a random thread) > > Ok thanks for the replies. > > Ok I think it's safe to proceed with the following: > - Stop mips1 builds (we don't have mips2) > - Reduce the frequency to once-a-year for mips3 and mips4. Updating > these stages every year with catalyst will be a lot of fun ;) > > @kumba: You mentioned too many times that I wanted to "drop" support for > mips3 and mips4. I never said that (I am sort-of tired keep repeating > that). All I said (again) was to reduce the frequency or stop building > them at all. Users can still get an existing mips3/mips4 stage3 and > update themselves > mipsel3 is used for the lemote. Are you sure we should drop it? -- Anthony G. Basile, Ph. D. Chair of Information Technology D'Youville College Buffalo, NY 14201 (716) 829-8197