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 11F4B1381FA for ; Mon, 5 May 2014 14:07:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 801C1E0B78; Mon, 5 May 2014 14:07: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 054BCE0B78 for ; Mon, 5 May 2014 14:07:41 +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 AB3C7340238; Mon, 5 May 2014 14:07:40 +0000 (UTC) Message-ID: <53679ACC.3000809@gentoo.org> Date: Mon, 05 May 2014 15:06:04 +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 CC: releng@gentoo.org Subject: [gentoo-mips] Reducing the number of the MIPS supported stages Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 9fdfd6f6-9151-42f3-a6e2-43f45a5c4e15 X-Archives-Hash: 66965a402cc2a04a878125e981db5407 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? (CC'ing releng just to keep them in the loop) -- Regards, Markos Chandras