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 F2BC21381FA for ; Tue, 6 May 2014 07:08:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B9CF9E09FF; Tue, 6 May 2014 07:08:42 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 424ABE09FF for ; Tue, 6 May 2014 07:08:42 +0000 (UTC) Received: from [192.168.1.2] (0545b819.skybroadband.com [5.69.184.25]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: hwoarang) by smtp.gentoo.org (Postfix) with ESMTPSA id F34933403EF for ; Tue, 6 May 2014 07:08:40 +0000 (UTC) Message-ID: <53688A17.2070509@gentoo.org> Date: Tue, 06 May 2014 08:07:03 +0100 From: Markos Chandras User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.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> In-Reply-To: <53682856.5040005@gentoo.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: e5a4549e-7fe0-437d-bd96-6cb1ebcee3a3 X-Archives-Hash: a4fa8143ef9b9bb850ef0d9fe8374389 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 -- Regards, Markos Chandras