A History of PowerPC
A reader writes: "There's a article about chipmaking at IBM up at DeveloperWorks. While IBM-centric, it talks a lot about the PowerPC, but really dwells on the common ancestory of IBM 801" Interesting article, especially for people interested in chips and chip design.
I still want a PPC ATX board. Pegasos was supposed to deliver, but their boards are still so expensive. :-(
/* oops I accidentally made a comment, sorry */
John.
Gone where the intelligent disk and network subsystems. No more die cast aluminimum chassis.
Whilst I can understand in some sectors the incessant drive for highest MIPS per $, is there not also a place for bullet proof proven technology?
And if you thought that was boring you obviously havn't read my Journal ;-)
I don't see how computer history that goes back to the 1960s can fail to be "IBM-centric." Remember, these were the big guys Microsoft was afraid of pissing off in the 1970s and 1980s. No one ever got fired for buying IBM, because they pretty much wrote the book on chip design before Intel hit it big.
(Which is great until you mispredict a branch, of course. :-)
Can anyone tell me where I can buy a G5 laptop?
Expanding the data to 64 bits has no effect on existing code, whereas the big-endian case will have to change all the pointer values
So, you're reading in an array of integers, which are now 64 bit vs 32 bit and no code change is needed?
Programs NEED to know the size of the data they're working with. Simply pulling data from an address without caring for it's size is a recipee for disaster!
"That's so plausible, I can't believe it!" - Leela
RISC made each instruction simple. That's how the name was chosen. But the point of machine each instruction simple was so that every transistor could be used in each cycle. By using every transistor, you maximize your performance on a per-transistor basis.
So, to do this, you drop specialized functionality. This meant simplifying the instruction set.
But that produced code bloat, because to really follow the idea you have to ditch stuff like dividers. Dividers are very difficult to fit into a pipeline and so the proper way to follow the mantra is to to expand a division into 32 separate instructions that do one step of the process (or 17 stages with other dividing methods). These 32 instructions could be pipelined, and thus you maximized your transistor reuse.
But this leads to code bloat. At the minimum, you have to do some call setup and takedown to call a division function. So that hardware was put back in. And other hardware followed, until even specialized vector units are allowed.
CISC can produce good performance also if they can utilize all their transistors better.
Well Motorola hoped the PPC would be the successor to the M68k, a very successfull processor that was very widely used, easy to program for and very good for learning assembly on.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!