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 94FB11381FA for ; Mon, 5 May 2014 17:13:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E69C7E0ACF; Mon, 5 May 2014 17:13:49 +0000 (UTC) Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 60B7BE0ACF for ; Mon, 5 May 2014 17:13:48 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id wm4so1929755obc.26 for ; Mon, 05 May 2014 10:13:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=specialbusservice.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=zWxZNBcSkXG6MOVqo/ZUVXnSjkk4vzd3KeWaULjRSUw=; b=ljX3HWH8mUG39GN2EEqsCi6dNW5K0sYDZV+qsrrQCa8r5ka4VbK2QDg9Ain2AflXkO i/Fv7CFprehkaE3FmUjSjXA05lr54Or1epLwjQCzKuIOwiSqD76GwyUeC755nXzKDEQQ rxx5HuuHsKaupVzme/ucaTNGj+Miytfl2hG/M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=zWxZNBcSkXG6MOVqo/ZUVXnSjkk4vzd3KeWaULjRSUw=; b=C55MvK+FJPurhYTOirq5iklMqaUeeaYjDMN5j1kBtauvmtMpYAuPlwKsU9bkhJd5S1 XtfXgeRxcHk55kjKYgyoIgATcSWmrrKn1KaK03LX6P3Qi2OygvStqySPJ69B8oncjj7J BfAPxc4arWf7rjEcAu1t6gBam/zbZR5/1AG7VkgdHPG/py6rwwcyseLe0Kz8rZ8Bhs3N RIEIArwWXMQQx4Xb/unLpXeQk+mUR0nFZWIr7904L1kRqCJkk4KVGgkk1Bfz+jndpif6 j/xjMh4vWEeLtnuSD2QEVqFG8exknfV4hRmeGZQf5YywStwz4UAggjkpGPKfbaeuQ1w6 rcWA== X-Gm-Message-State: ALoCoQlAzbTuVa5dztZFnFrBnrurA9RNQfO/14bjuD9CS8hb/Rx4NUJaZzs35k68HBVbQ7FlYg6F 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 X-Received: by 10.60.130.195 with SMTP id og3mr11645055oeb.36.1399310028035; Mon, 05 May 2014 10:13:48 -0700 (PDT) Received: by 10.182.10.5 with HTTP; Mon, 5 May 2014 10:13:47 -0700 (PDT) Received: by 10.182.10.5 with HTTP; Mon, 5 May 2014 10:13:47 -0700 (PDT) In-Reply-To: <53679ACC.3000809@gentoo.org> References: <53679ACC.3000809@gentoo.org> Date: Mon, 5 May 2014 18:13:47 +0100 Message-ID: Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages From: Justin Cormack To: gentoo-mips@lists.gentoo.org Content-Type: multipart/alternative; boundary=089e01176dd5273b8b04f8aa4120 X-Archives-Salt: 5a2701c2-ca32-4056-b750-c2b74ff295c3 X-Archives-Hash: db1ef2fa4f38e2eaec3d87daa0dace70 --089e01176dd5273b8b04f8aa4120 Content-Type: text/plain; charset=UTF-8 On May 5, 2014 3:07 PM, "Markos Chandras" wrote: > > Hi all, > > Right now the number of stages for each endianness is 8: > > - mips1 > - mips32 > - mips32r2 > - mips3 > - mips4 > - mips4_r10 > - mips64 > - mips64r2 > > ==> 16 stages in total. > > This takes quite a bit of time for all stages to be built (by the time everything is built, we are one month passed the time the snapshot was taken). How about stop building stages for mips1, mips3 and mips4? We keep the existing stages on the mirrors but we will no longer update them (or maybe we do on per user or per case basis). I understand there is hardware for these ISAs but how often do people actually use the new stages? > > Just to be clear, I am not suggesting for the team to stop supporting these ISAs but to stop building new stages and let the users of such ISAs, grab an old stage3 and do the update themselves if needed. > > This will free up some hardware resources for building different stages for the newer ISAs (maybe more non-multilib n32 and n64 variants etc) > > What does everyone think? > Agree in general but not quite sure about the choice. Mips3 (fuloong) is still quite widely used I think. Mips32 might not be though, Android seems to be mips32r2 Has anyone asked Imagination for resources to support this? Justin --089e01176dd5273b8b04f8aa4120 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On May 5, 2014 3:07 PM, "Markos Chandras" <hwoarang@gentoo.org> wrote:
>
> Hi all,
>
> Right now the number of stages for each endianness is 8:
>
> - mips1
> - mips32
> - mips32r2
> - mips3
> - mips4
> - mips4_r10
> - mips64
> - mips64r2
>
> =3D=3D> 16 stages in total.
>
> This takes quite a bit of time for all stages to be built (by the time= everything is built, we are one month passed the time the snapshot was tak= en). How about stop building stages for mips1, mips3 and mips4? We keep the= existing stages on the mirrors but we will no longer update them (or maybe= we do on per user or per case basis). I understand there is hardware for t= hese ISAs but how often do people actually use the new stages?
>
> Just to be clear, I am not suggesting for the team to stop supporting = these ISAs but to stop building new stages and let the users of such ISAs, = grab an old stage3 and do the update themselves if needed.
>
> This will free up some hardware resources for building different stage= s for the newer ISAs (maybe more non-multilib n32 and n64 variants etc)
>
> What does everyone think?
>

Agree in general but not quite sure about the choice. Mips3 = (fuloong) is still quite widely used I think. Mips32 might not be though, A= ndroid seems to be mips32r2

Has anyone asked Imagination for resources to support this?<= /p>

Justin

--089e01176dd5273b8b04f8aa4120--