/prog/ CPU project

Instruction set is as follows:

IHBT   Copy one registar to another

>>1 May i suggest usign OpenCores as reference and inspiration: http://en.wikipedia.org/wiki/OpenCores



_______________________________
http://xs135.xs.to/xs135/09042/av922.jpg
What actually transpires beneath the veil of an event horizon? Decent people shouldn't think too much about that.

>>3
um... no?

>>4
YHBT pushes to the stack.

>>5 Syntax conflict with 'HBT which is register-to-register op



___________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
The basic objectives and principles of war do not change.The final objective in war is the destruction of the enemy's capacity and will to fight, and thereby force him to accept the imposition of the victor's will.

HMA clears the interrupt flag and sets the trap flag

"GRUNNUR" randomly swaps two bits in each of the registers.

>>8 and where does this randomness comes from?



______________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
I think, and my thoughts cross the barrier into the synapses of the machine - just as the good doctor intended. But what I cannot shake, and what hints at things to come, is that thoughts cross back. In my dreams the sensibility of the machine invades the periphery of my consciousness. Dark. Rigid. Cold. Alien. Evolution is at work here, but just what is evolving remains to be seen.

>>9
It's not too difficult to make a hardware random-number generator and fucking piss easy if you settle for pseudo-randomness. With hardware, you could use a thermocouple and generate the bytes based on the noise.

>>10 You have to specify how this works for the 'GRUNNUR' opcode(like
(init rng with timer) ,rng -> get_rnd_location_source,rng-> get_rnd_location target, bit_swap[source[loc1]][target[loc2]].


__________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
A government big enough to give you everything you want, is big enough to take away everything you have

>>11
It is left as an excercize for the implementer.

example:
opcode GRUNNUR(reg1,reg2){
rng_seed(timer);
rng_gen();src_bit=rng%64;
rng_gen();targ_bit=rng%64;
swap(reg1[src_bit],reg2[targ_bit]);
}



_________________________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
When everyone thinks the same, nobody is thinking.

>>13
We don't care how each one will be implemented, this thread is about defining an instruction set, which you have not contributed towards at all.

FrozenVoid there is no reason that a single opcode shouldn't be capable of performing a complicated, but useful, task. Especially given that, as I already stated, it is possible to do it completely in hardware. (Inb4 someone points out that it is theoretically possible to make any program in hardware) Yes, IHBT

On a similar note, we need a TROLLOP opcode, it causes a hardware reset.

The infix >>= operator.

reg1 >>= reg2 will bind the monad in reg1 to the one in reg2