What actually would make some sense however is to compile the entire linux kernel directly to VLIW and include the code morphing engine as part of the kernel. Now you would have to compile/morph only the user aplications at load-time. Remember that it takes a long time to load an application from disk so you could as well compile it on-the-fly without much overhead. You would basically overlap the disk delay with the time to do the compiling/morphing. This is more or less how FX!86 worked. (FX!86 was a x86 emulator for Alpha that beat most x86 CPUs at this time) It also makes memory management a lot easier.
I am shure they hired Linus to do this but later changed plans and focused on Windows.
Slashdot Mirror
This doesn't make a lot of sense.
What actually would make some sense however is to compile the entire linux kernel directly to VLIW and include the code morphing engine as part of the kernel. Now you would have to compile/morph only the user aplications at load-time. Remember that it takes a long time to load an application from disk so you could as well compile it on-the-fly without much overhead. You would basically overlap the disk delay with the time to do the compiling/morphing. This is more or less how FX!86 worked. (FX!86 was a x86 emulator for Alpha that beat most x86 CPUs at this time) It also makes memory management a lot easier.
I am shure they hired Linus to do this but later changed plans and focused on Windows.