public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: Matt Turner <mattst88@gentoo.org>, gentoo-mips@lists.gentoo.org
Cc: releng@gentoo.org
Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages
Date: Mon, 05 May 2014 18:29:40 +0100	[thread overview]
Message-ID: <5367CA84.40004@gentoo.org> (raw)
In-Reply-To: <CAEdQ38FXwAdL-61br_haW-XvGP2Zv9+Q4L2qzQ1fykM7kOfftw@mail.gmail.com>

On 05/05/2014 06:22 PM, Matt Turner wrote:
> On Mon, May 5, 2014 at 7:06 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
>> Hi all,
>>
>> Right now the number of stages for each endianness is 8:
>>[...]
> 
> Do we need r1 and r2 stages?

Why not? r2 has been around ~10 years. But r1 devices are still present.

> 
>>
>> ==> 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?
> 
> How often are you building stages?
Roughly every 3 months.

> 
> Resources aren't a problem but it takes a month to build everything?
Well, my free time is also limited so it's not just the resources that
may or may not cause some problem :) Preparing catalyst and solving
blockers in ~arch takes a considerable amount of my Gentoo time.

> Don't you have a 16 or 32-core build system? Cavium gave me ssh access
> to one that I was planning to build stages on, but I never tried.
> 
> I guess I don't understand the problem you're facing.
> 

My question (and not a problem) is whether building stages for old ISAs
is desired or not. If it is, then that's fine. If not, then maybe we can
stop building stages or maybe we can build them once a year? Like you
said, with the additions of newer ISAs (like -r3) the total number of
stages will grow even more. I think we are the arch with the most stages
in Gentoo, which is a great thing(!) but maybe we can reconsider our
options, and make room for newer ISAs and variants?

-- 
Regards,
Markos Chandras


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

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=5367CA84.40004@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-mips@lists.gentoo.org \
    --cc=mattst88@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