Compiler Ownage

I am starting to think that I will definitely need to port a C/C++ compiler over to my own processor. The reason is one of freedom. Constantly relying on other people to write the compilers mean that I am constantly constrained by the existing architectures. I think that I am done learning through copying. I have just started to improve existing architectures. My next step should be to create my own architecture from scratch.

I have been attending a training this week, learning how to attack patents and to develop new IP. It has been an eye-opening experience for me and I really have learned a lot. Some of you may be confused as to why an anti-patent person would be attending such a training. Sun Tzu said, “know your enemy and know yourself, find naught in fear for 100 battles. Know yourself but not your enemy, find level of loss and victory. Know thy enemy but not yourself, wallow in defeat every time.”

So, after knowing how to design and build the various sub-systems of a processor, and also learning on the various theoretical architectures out there, it is now time for me to build a processor based on my own architecture to fix my own problems. I have some ideas on what features these processors might have. However, I do not know where it will ultimately lead me.

Being in control of the entire stack from hardware, compiler through to operating system and application software would be very useful indeed. It would allow me to explore further than before.