An AMD Core 2 Duo. Right..........................nute wrote:First off, lower color density is faster. Second off, having a monochrome monitor even if you are running on
an AMD Core 2 duo is a good way to keep people from playing games.
You have an odd set of priorities. Keep people from playing games? Why the blazes would we care about that?
Let's see, base system requirements for ROS these days is 100-200 MHz with 32MB of RAM. Whether you'd be able to do anything useful on such a system is another matter entirely, since there'd be no RAM left over for applications to use.
I'm seriously questioning your intelligence here. You're making claims here that any liable to fail you in any introductory computer engineering or introductory programming class if you tried to actually carry them through, at least the ones I took.
Programming on an older system does NOT mean you are forced to program more efficiently. If you are that obsessed with this so-called optimization, then go learn embedded programming. Then maybe you'll realize just how much functionality you lose when trying to program things under such resource constraints. People programming on those systems take a different approach, one that is often not directly applicable to the programming of desktop or server systems. They essentially do less with less, wherein on a desktop system the idea is to do more with less. On embedded systems, the more part is usually not possible.
The military has a radiation hardened version of the Pentium designed to survive EMP blasts due to detonating nukes.
You "encourage designing ROS so that Pentium specific instructions are isolated." And what exactly do you think this project has been doing? Usage of assembly code is kept to an absolute minimum so that porting to different architectures is easier. But we explicitly chose to ignore the pre-Pentium Intel processors because there's no reason to bother supporting them. Any modern Windows NT application that you would want to run is almost guaranteed to not work on those systems and an OS is useless without applications. Hell, I wouldn't even have the patience to test applications on something that old and weak, much less use it for daily activities.
Let's see. Prove that using a subset of the Pentium's instructions slows things down. Well, not using the cmpxchg instruction would definitely slow things down. Then there's the lack of MMX and SSE as you already pointed out, though that's more an application side loss. But hell, you've already taken a major performance hit with the loss of the atomic compare and exchange instruction. The rest are just more nails in the coffin.
So far I have yet to see any actual reason for wanting to support pre-Pentium Intel processors. They're too slow to actually run even Windows 95 era software and they're actually incapable of running applications that make use of vector processing extensions.
An additional note from Timo. 32bpp is actually faster than 16bpp since on (relatively) modern system 32bits is the natural machine word size.