The author (Mark Smotherman, Associate Professor, School of Computing, Clemson University) makes an effort to list the key computer architects mainly to recognize their work. The listing comprises instruction set architectures (ISAs) and their architects, followed by implementations of each ISA and the associated microarchitects and designers. The processors listed have been available for sale commercially, and in most instances they are grouped by company. The list mainly covers ISAs and microprocessor implementations of the late 1980s and 1990s, and it especially highlights high-performance (that is, high-risk) implementations.
Why a list of names matters
Most people can name the company behind a famous processor. Far fewer can name the people who defined its instruction set or designed its pipeline. Smotherman's page fills that gap. It reads like a credits list for computing: for each machine, who set the architecture, who led the implementation and who built the key parts.
The page opens with a quotation that explains the point of the exercise:
The success and failure of high risk computer developments can quite often be traced to a single individual. It is not accidental that unique persons such as Gene Amdahl, Seymour Cray, Fred Brooks, and Bob Barton have become recognized leaders in the computer architecture and design field. Their reputations did not arise from a happy coincidence of being associated with a successful project; rather, they stand out because of their ability to generate a system wide concept, determine a course of action to get it implemented, make the necessary tradeoffs and finally drive through all obstacles to ensure completion of their vision.
The page credits this passage to Neil Lincoln of Control Data Corporation (CDC), from his essay "It's really not as much fun building a supercomputer as it is simply inventing one", published in High Speed Computer and Algorithm Organization (Kuck, Lawrie and Samek, eds., Academic Press, 1977).
Architect versus microarchitect
The list keeps two roles apart, and the distinction is worth knowing:
- The architect defines the instruction set: the instructions, registers, addressing modes and memory model that software sees. This is the contract between hardware and software.
- The microarchitect or designer builds a particular implementation of that contract: the pipeline, caches, branch prediction and circuits. One ISA can have many implementations, each with its own design team.
That is why the list gives each ISA first and then its implementations. In the companion survey described below, Don Alpert credits IBM's System/370 with formalizing and exemplifying this distinction.
How to use the page
The page is long, so treat it as a reference rather than a read-through. It has a numbered table of contents by processor class: supercomputers, VLIW, mainframes, minicomputers, microcomputers, workstations, embedded processors, DSPs, game processors and more. Within each class, entries are mostly grouped by company. The page notes that it may have omissions and that credit for a design is sometimes disputed, and it invites corrections. When this post was updated, the page said it was last updated in May 2025.
Also read: Which Machines Do Computer Architects Admire?
Deep dive: the numbers and details
This part holds examples from the list and the results of the companion survey. Skip it if the overview is all you need.
Ten examples from the list
These entries are taken from Smotherman's "Who are the Computer Architects?" as it stood when this post was updated. The roles are as the page gives them.
| ISA and year | Architect(s) named on the page |
|---|---|
| CDC 6600, 1964 | Seymour Cray (project lead), Jim Thornton (CPU) |
| IBM System/360, 1964 | Fred Brooks (project manager), Gene Amdahl (architecture manager), Gerrit Blaauw (second architect and author of the manual) |
| Cray-1, 1976 | Seymour Cray (architect), Lester Davis (chief engineer) |
| Motorola 6809, 1979 | Terry Ritter and Joel Boney |
| Zilog Z80 | Masatoshi Shima |
| MIPS-I, 1986 | Craig Hansen, chief architect |
| SPARC versions 7 and 8, 1986 and 1990 | Robert Garner, chief architect |
| Intel i860 (N10), 1989 | Les Kohn |
| DEC Alpha | Dick Sites and Rich Witek |
| Intel IA-64, 1997 | John Crawford, chief architect |
The "admired machines" survey
The companion page, "Which Machines Do Computer Architects Admire?", grew out of the Toolsmith Conference held in Chapel Hill, North Carolina, in October 2001 to honor Fred Brooks, chief architect of the IBM S/360. After the conference the author asked several computer architects which machines they admired and published their answers with permission. Respondents include Don Alpert, Josh Fisher, Mark Hill, Yale Patt, Dave Patterson, Dick Sites, Jim Smith, Guri Sohi, Steve Wallach, Sophie Wilson and Bill Worley, with Gordon Bell added later.
Counting the "primary machines" section of that page:
| Machine | Times listed |
|---|---|
| Cray-1 | 6 |
| MIPS | 5 |
| CDC 6600 and 7600 | 4 |
| IBM S/360 and S/370 | 4 |
| PDP-11 | 3 |
The answers are worth reading for the reasons rather than the votes. Don Alpert, for example, explains what the System/370, the PDP-11 and MIPS each taught him, including his early doubt that so simple an architecture as MIPS could perform so well.
How to study a machine from the list
- Start with the ISA: register count, instruction formats and addressing modes. These show the architect's priorities.
- Then read about one implementation: pipeline depth, issue width and cache organization. These show the microarchitect's trade-offs for a given technology.
- Compare two implementations of the same ISA built years apart. The differences show how technology changed the best design while the software contract stayed fixed.
Further reading
- Mark Smotherman, Who are the Computer Architects? (Clemson University)
- Which Machines Do Computer Architects Admire? (Clemson University)
- MIT 6.823 Computer System Architecture Lecture Notes (this blog)

hello... hapi blogging... have a nice day! just visiting here....
ReplyDeleteHello!!
ReplyDeleteI had just visited your blog and liked it a lot. Would you like to exchange links with my domain? It would be great if you agreed.
You can visit my domain: www.gnagri.net
nice post
ReplyDeleteCheck this: http://only-vlsi.blogspot.com/
nice article.
ReplyDelete