Deprecate 601 based systems

[GoogleCodeExporter]

In issue 2, we already had some issues with 601-based systems while trying
to port TraceMonkey. I have decided not to do this port for 9.2.x, but I
would like to try again in the future.

Dropping 601 has other advantages, especially since we can now optimize for
603 and get some small improvements. The chief disadvantage is this almost
completely excludes any possibility of a 68k Mac running Classilla with a
PPC upgrade card except for the few 68Ks that can use a 603 (Blackbirds
come to mind), and possibly the 7200. The x100 and 7500, however, can be
upgraded to G3 or better, so they should still operate.

Field reports from Brian Deuel indicate that the 6100 already can't run
Classilla with maximum RAM installed, so it may not be possible to run it
anyway.

Nevertheless:

Starting in 9.2, the minimum system requirement will be a 603 processor,
though no attempt will be made to deliberately exclude 601 users. A
Gestalt() check in the apprunner will warn 601 users that their system is
unsupported and to contact me so I can start getting a headcount.

Starting in 9.3, assuming I do not abort this switchover, I will start
converting the MCPs to optimize and use 603 instructions.

This won't affect me porting Classilla to the BeBox one day, since the
BeBox is 603-based.

If you are using Classilla on an non-upgraded 601 based Power Macintosh,
speak now.

Original issue reported on code.google.com by classi...@floodgap.com on 26 Apr 2010 at 1:47

• Blocking: #2

[GoogleCodeExporter]

After user feedback, this change will not occur in 9.2. Somewhere between 9.3 
and
9.4, the Gestalt check will be added, and in 9.4 I intend to take another crack 
at
TraceMonkey and end 601 compatibility. With this strategy, 601 users will at 
least
have SpiderMonkey and the updated layout before support ends for those 
machines, and
I do hope to have security patches up between 9.3 and 9.4 as well.

Original comment by classi...@floodgap.com on 17 May 2010 at 6:50

• Added labels: Priority-Low
• Removed labels: Priority-Critical

[GoogleCodeExporter]

I'm also toying with a 601-specific JavaScript shlb using mfrtc instructions, 
but I
don't know how well that will work.

Original comment by classi...@floodgap.com on 17 May 2010 at 6:51

[GoogleCodeExporter]

Is there a way you could make two builds, one for ancient 601 Macs and another 
for 603+ ones? Besides, I'm pretty sure that if you have a 601 Mac, Javascript 
will drive that poor little thing crazy. Javascript sometimes feels sluggish on 
my G3 iMac, so maybe just make a build with the old JS engine from the current 
Classilla builds for 601 Macs, and a modern version for 603+ Macs? I'm not a 
programmer or anything, so I barely know what I'm talking about, please excuse 
me if I'm speaking rubbish that could never happen.

Original comment by mustangz...@gmail.com on 14 Oct 2010 at 10:18

[GoogleCodeExporter]

Actually, now that I've worked on TenFourFox's nanojit, and seen how it 
operates, we can work around the 601 issues, so changing this to WontFix.

Original comment by classi...@floodgap.com on 26 Jan 2011 at 5:53

• Changed state: WontFix