Good point about static analysis and C code. That means you would not be able to toss memory protection unless you introduce fast hardware support for bounds ch

Good point about static analysis and C code. That means you would not be able to toss memory protection unless you introduce fast hardware support for bounds checking and bounds check everything in JITed code. I guess you could also have the JIT do more elaborate guarding of memory but that would probably have a performance penalty. You could still toss a lot: virtualization, complex multi-layered protection modes, address remapping, and essentially every hardware feature that exists to support legacy binary code. All deprecated instructions and execution modes could go, etc. Finally you would maintain the benefit of architecture flexibility. Switching from x86 to ARM, etc., would be easy.