Why not go with 64 bytes and just scrap the whole RAM idea XD. Though if you are pipelining like you wish, I do suggest 64 bytes. While you may not fill it up, the peice of mind along with the fact that 16 could be too little.
Perhaps 32 bytes? Happy medium?
I decided to go with 16 because it turns out that the total circuit time is 18 ticks, and so I will always have 2 registers without data in the loop. Also it's a convenient size
lol. I'm actually having trouble making the registers for the pipeline since i need a lot for it to be feasible and they add a lot of delay. Do you think 16 bytes is enough or should i do 64 like i had originally planned?
Not a redstone expert neither, but I know that it's necessary for making a redstone computer, and it has to do with something that makes computers work in reallity.
Benny created a 2-tick fully synchronized one. Although that used pistons...
Because it uses pistons you cannot pipe data through at more than a 4 tick interval regardless of the time it takes data to move through it. His ALU is more useful in a non-pipelined cpu. Mine will be used for a very rapid data pipeline. I will probably do a followup video on it later to show its application. It will probably be most useful in graphics processing where you must perform the same operation on large amounts of data.
I am beginning work a 3 tick pipelined computer using this ALU. I will be using some rudimentary forms of branch prediction to aid in some programs. The cpu will have 2 modes: one being a pipeline and the other not. This will be useful for programs relying on the most recent output to further process data.
Progress:
ALU and Registers: 100% *Tested and works perfectly!*
CPU Functions: 10% (I've decided on the functions, now I must implement them! This will perform many vector operations and matrix operations that can be easily used in graphics processing)
Instruction Set: 10%
0
0
I decided to go with 16 because it turns out that the total circuit time is 18 ticks, and so I will always have 2 registers without data in the loop. Also it's a convenient size
0
lol. I'm actually having trouble making the registers for the pipeline since i need a lot for it to be feasible and they add a lot of delay. Do you think 16 bytes is enough or should i do 64 like i had originally planned?
0
Well, thankfully the carryout actually generates 2 ticks before the alu outputs and so I have just enough time to halt the pipeline if needed
0
lol speak for yourself the pipeline for the computer will be 3 tick with a 24 tick clock
0
Lol XD
0
lol thanks
0
It does the math in a cpu
0
indeed, but calculator is a bit vague. it performs addition, subtraction, and bitwise boolean logic
0
0
Because it uses pistons you cannot pipe data through at more than a 4 tick interval regardless of the time it takes data to move through it. His ALU is more useful in a non-pipelined cpu. Mine will be used for a very rapid data pipeline. I will probably do a followup video on it later to show its application. It will probably be most useful in graphics processing where you must perform the same operation on large amounts of data.
0
lol yeah it's sorta to grab people's attention, but it is true in terms of thru-put XD thanks for checking it out
2
I am beginning work a 3 tick pipelined computer using this ALU. I will be using some rudimentary forms of branch prediction to aid in some programs. The cpu will have 2 modes: one being a pipeline and the other not. This will be useful for programs relying on the most recent output to further process data.
Progress:
ALU and Registers: 100% *Tested and works perfectly!*
CPU Functions: 10% (I've decided on the functions, now I must implement them! This will perform many vector operations and matrix operations that can be easily used in graphics processing)
Instruction Set: 10%
0
2