Continuation-Passing Style Assembler

Ukrainian guy an implemented OSIC based on Scheme compiler and automatas from Wolfran's book:
http://mazonka.com/st/bbj42.pdf

each opcode takes the address of the next opcode, and everything does self modification of everything. Try writing a decompiler for that, Cudder!

Such OSICs give very good massively parallel performance, if the memory size is small. Even FPGA OSICs easily beat real CPUs.

How do you pipeline OISC?

>>3
Self-modifying code can't be pipelined, dolt.

>>4
Yes, it can. You just have to make sure that the next N instructions are constant.

>>5
You can't determine that without executing them.

>>6
Wrong

>>4
put this in ur pipeline *grabs dick*

Lol. They made an entire OS running on OSIC FPGA
https://www.youtube.com/watch?v=dlxMy_zrgAU

Terry Davis tier schizophrenia.

>>9
The source code is just something. The schizo named everything in Hungarian, so there are variables like PROCESSZOROK_ADAT, idonkentkirajzol and munkaciklus

hile other mainstream operating systems are content consuming operating systems designed only for communication and content consume, Dawn operating system was designed to supply a computing platform, where the user have full control over the hardware. Dawn requires no connection with foregin servers to operate: there are no thousands of mistic packages or strange updates to download to use Dawn. Dawn operating system has everything to achieve something no other operating system from this era can supply for you: computing. Dawn offers a mature traditional user interface and friendly apperance to help you while you work, learn, do scientifical simulations, write and run your own programs, or play. Everything is fun and happyness under Dawn

http://esoteric.codes/post/168290778358/a-programming-language-with-only-one-command-and

i had no clue what platform should i target. i originally planned x86, but i realized how bad it is - after all, current x86 is the result of approx 30+ years of work of 1 million hardware developer, all added his own poop into it to have a cpu. some idiot waked up at morning, and decided to add a MOV with his very own shitty prefixes and various different encodings. another idiot waked up at morning, and decided to add a floating point instruction which adds integers to floating point, and stores the results in a floating point register. another idiot waken up, and decided to add an opcode for adding 4 numbers simultanously. 1500 idiot waken up, added his own opcode, various memory addressing modes, and todays x86 has been born, with one billion transistors minimum just to have an operating system boot. not to mention every opcode has random lenght, and encapsulates a semi-undocumented segmentation, which creates an x86 so complex, that our x86 cpus are actually risc cpus emulating x86. no corporation can make x86 processors any more, they are so complex at least 20 years of work from a 10000 ic design professional persons would need it to even have windows booted (not to mention that a compatible io system also must be created). x86 is a form of opression, one of the main reasons we didnt had any real step forwards.

Take that, you cudder!

>>12
If you thought x86 was bad, go look at AArch64...

>>5
Alternatively, a pipelined OISC core might forward the modified instruction like x86 has done for ALU results since the '486.