public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Cc: releng@gentoo.org
Subject: Re: [gentoo-mips] Re: Reducing the number of the MIPS supported stages
Date: Mon, 05 May 2014 20:33:55 +0100	[thread overview]
Message-ID: <5367E7A3.3090503@gentoo.org> (raw)
In-Reply-To: <5367E42A.70105@gentoo.org>

On 05/05/2014 08:19 PM, Anthony G. Basile wrote:
> On 05/05/2014 10:06 AM, 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?
>>
>> (CC'ing releng just to keep them in the loop)
>>
> 
> FYI, for uclibc I'm only doing big endian mips32r2 and little endian
> mips3 (aka mipsel3).  Those are in use (atheros ar71xx boards and
> lemote, respectively).
> 
> Since you can build a lower level ISA on a board capable of a higher
> level ISA, maybe you want to choose along those lines, eg you can build
> mips1 using catalyst on an ar71xx board running mips32r2.
> 

Yes there are a lot of options. Sadly we have no metrics on how many
people use the old ISA stages or how many of them build their own thing.
I don't want to decide anything by myself, I want to know what others
think and make a decision as a team and community (if we are going to
decide anything at all) :)

-- 
Regards,
Markos Chandras


      reply	other threads:[~2014-05-05 19:35 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
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 [this message]

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=5367E7A3.3090503@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-mips@lists.gentoo.org \
    --cc=releng@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