|[4 earlier articles]|
|Re: The RISC penalty jbuck@Synopsys.COM (1995-12-20)|
|Re: The RISC penalty email@example.com (1995-12-21)|
|Re: The RISC penalty firstname.lastname@example.org (1995-12-28)|
|Re: The RISC penalty email@example.com (1995-12-28)|
|Re: The RISC penalty firstname.lastname@example.org (1995-12-30)|
|Re: the RISC penalty john.r.strohm@BIX.com (1995-12-30)|
|Re: the RISC penalty email@example.com (1995-12-31)|
|From:||firstname.lastname@example.org (Peter Klausler)|
|Date:||31 Dec 1995 12:05:40 -0500|
|Organization:||at home in Minneapolis|
|References:||95-12-132 95-12-154 95-12-156|
Michael Meissner wrote:
>Well it depends on how you view the instruction stream. True variable
>sized nstructions are a pain, but did it in terms of 60-bit words (ie,
>instructions would not cross a word boundary, so if you wanted to use a
>30-bit instruction, and there are only 15 bits left in the word, you have
>to put a NOP, and start on the next word).
>This was true of the lower-end machines, but was NOT true of the 6600 and
>higher machines. They had the 8-word instruction stack (a microscopic
>instruction fetch cache), and could handle 30-bit instructions that spanned
Just for historical accuracy: the instruction stack was indeed 8 words, but
one of them held the "next instruction word" fetched from after the loop,
so the challenge was to squeeze the code into SEVEN words. There was a
library called STACKLIB containing routines thus optimized.
Also, the 6600, etc., used word addresses to address code, so the
assembler had to insert NOPs (inst 046) to "force upper" before
labels to get them properly aligned.
Sigh. Programmers never get to have this much fun any more.
Puzzling out multiple inheritance just doesn't compare. :-)
Source: Assembly Language Programming for the Control Data 6000
and Cyber Series by Grishman, a wonderful book, dedicated to A6
and A7, "without which none of the results in this book could
have been saved."
Peter Klausler (email@example.com) "They're beating my head against a dead horse."
Return to the
Search the comp.compilers archives again.