| 1 |
On May 5, 2014 3:07 PM, "Markos Chandras" <hwoarang@g.o> wrote: |
| 2 |
> |
| 3 |
> Hi all, |
| 4 |
> |
| 5 |
> Right now the number of stages for each endianness is 8: |
| 6 |
> |
| 7 |
> - mips1 |
| 8 |
> - mips32 |
| 9 |
> - mips32r2 |
| 10 |
> - mips3 |
| 11 |
> - mips4 |
| 12 |
> - mips4_r10 |
| 13 |
> - mips64 |
| 14 |
> - mips64r2 |
| 15 |
> |
| 16 |
> ==> 16 stages in total. |
| 17 |
> |
| 18 |
> This takes quite a bit of time for all stages to be built (by the time |
| 19 |
everything is built, we are one month passed the time the snapshot was |
| 20 |
taken). How about stop building stages for mips1, mips3 and mips4? We keep |
| 21 |
the existing stages on the mirrors but we will no longer update them (or |
| 22 |
maybe we do on per user or per case basis). I understand there is hardware |
| 23 |
for these ISAs but how often do people actually use the new stages? |
| 24 |
> |
| 25 |
> Just to be clear, I am not suggesting for the team to stop supporting |
| 26 |
these ISAs but to stop building new stages and let the users of such ISAs, |
| 27 |
grab an old stage3 and do the update themselves if needed. |
| 28 |
> |
| 29 |
> This will free up some hardware resources for building different stages |
| 30 |
for the newer ISAs (maybe more non-multilib n32 and n64 variants etc) |
| 31 |
> |
| 32 |
> What does everyone think? |
| 33 |
> |
| 34 |
|
| 35 |
Agree in general but not quite sure about the choice. Mips3 (fuloong) is |
| 36 |
still quite widely used I think. Mips32 might not be though, Android seems |
| 37 |
to be mips32r2 |
| 38 |
|
| 39 |
Has anyone asked Imagination for resources to support this? |
| 40 |
|
| 41 |
Justin |
Archives