> 
> I was thinking of doing this as an emulation package in the kernel,
> having the kernel load the emulator executable somewhere "out of the
> way" (as if by an address-unspecified mmap) and then turn control over
> to it after loading the executable itself "normally".  Then you could
> use, say, the VAX native toolchain, building VAX native executables,
> but running on some killer Alpha or something, far faster than a real
> VAX.  Of course, the emulation wouldn't be perfect; any kmem groveler,
> for example, is instant toast.  But it should be fairly straightforward
> to make it good enough to run the toolchain.
> 
I think this is a wonderful idea! I have written a (limited) VAX
emulator, so if you/someone have any idea about how this shall be
implemented I will happily fix the vax low-level parts :-)

-- Ragge