10-06-2014, 03:05 AM
All programs in MC to run at all fast need to be precompiled
The definition i am using of pipeline is the only definition, when u split up a single operation into steps then buffer those steps and have multiple inst being processed at different stages of the CPU simultaneously. not the same piece of hardware doing 2 things at once.
with the variable completion time u will have between ur mult/root/divide/square/add/sub.. you will have to have a system to track that, or have to precompile with those time frames in mind, cause all ops have to save and u cant save 2 at the same time unless u make one of the first dual write Reg.
just saying good luck with he instant wire,, the delay in bussing is generally needed for control lines and such, and instant just gets stuff all screwy.... and a CPU is a bit more complex then a osciliscope,
"quickly build" is never the case, any GOOD CPU takes time researching, thinking and designing as well as building... and being able to run multiple programs using more memory isnt the solution, u will run into problems with Context Switching/Swapping.. to which there are a few ways to make that faster, up to u how u do it tho. the best plan is to just do Call's and Returns, and have a main program like a "mini kernel" have a context switching protocol to do between every swap. to which u need a stack to transfer data between processes or u need to have programs access eachothers memory (that gets really fishy)
The definition i am using of pipeline is the only definition, when u split up a single operation into steps then buffer those steps and have multiple inst being processed at different stages of the CPU simultaneously. not the same piece of hardware doing 2 things at once.
with the variable completion time u will have between ur mult/root/divide/square/add/sub.. you will have to have a system to track that, or have to precompile with those time frames in mind, cause all ops have to save and u cant save 2 at the same time unless u make one of the first dual write Reg.
just saying good luck with he instant wire,, the delay in bussing is generally needed for control lines and such, and instant just gets stuff all screwy.... and a CPU is a bit more complex then a osciliscope,
"quickly build" is never the case, any GOOD CPU takes time researching, thinking and designing as well as building... and being able to run multiple programs using more memory isnt the solution, u will run into problems with Context Switching/Swapping.. to which there are a few ways to make that faster, up to u how u do it tho. the best plan is to just do Call's and Returns, and have a main program like a "mini kernel" have a context switching protocol to do between every swap. to which u need a stack to transfer data between processes or u need to have programs access eachothers memory (that gets really fishy)