Re: What do we call non-pipelined designs?

At university during the early 2000s we would've called it a multi cycle
design.
We had to design and implement on an fgpa an 8 bit multi cycle CPU using
the various design techniques in the fgpa software. It w as only a toy
with separate data and instruction memory that reused the ALU for
calculating instruction pointer etc , I can't even remember if we had a
call/return instructions or just branch and jump instructions it may
have had push,pop instructions or not, I do remember it using 16 bit
instruction words and roughly based on risc principles , I know I wrote
a quick and dirty assembler so I didn't have to manually translate
assembler to binary for the program ROMs.
I remember it going
Single Cycle : instructions take a single cycle and don't overlap
Multi Cycle : instructions take multiple cycles and don't overlap
optionally reusing parts on different cycle eg ALU , register file ,
different instructions could potentially take different number of cycles
Pipelined: instructions take multiple cycles but multiple instructions
overlapping , so need to deal with hazards.
We used the Hennessey and Patterson book 4th Ed from memory,  the first
one, not the second more advanced one, so I assume those are the terms
used in it.
We were just doing toy cpus to learn on , I doubt anybody needs to do
multi cycle designs anymore , those are from a time when gates were
precious.
If one layed it out like a pipeline but didn't have flip flops or
latches in between each stage would it still be pipelined? Ie is it
(single cycle,multi cycle)x(non pipelined,pipelined) or (single
cycle,multi cycle,pipelined). Then we could have degrees of pipelining ,
eg lightly,heavily, number of stages or numbers of gates(fo4 etc) of
delay.
Nick
--