4 ms·
My professor in college back in 1997 was doing research on maintaining binary compatibility between different generations of the same VLIW architecture. If you
by lizknope 5y ago
My professor in college back in 1997 was doing research on maintaining binary compatibility between different generations of the same VLIW architecture. If you had a different number of execution units and stuff like that. He had a few ideas and one of them was preprocessing the compiled binaries and rewriting them. Some of them were having flags in the architecture for what generation of chip they were to have the OS do on the fly changes
- twic 5y agoIn a world where all software is JITted (Java gang rise up), the fixedness of a VLIW ISA doesn't matter, because you always compile specifically for the target machine anyway. What you describe sounds like applying that strength of JITting to AOT-compiled code. Vaguely related ideas from the distant past are ANDF: https://en.wikipedia.org/wiki/Architecture_Neutral_Distribution_Format https://en.wikipedia.org/wiki/Architecture_Neutral_Distribut... And TaOS's VP Code: https://sites.google.com/site/dicknewsite/home/computing/byte-articles/the-taos-operating-system-1991#h.1yicc8orl6xd https://sites.google.com/site/dicknewsite/home/computing/byt...
- clacke2 5y agoThis is what IBM did with IBM i / AS/400 / System/38 and https://en.wikipedia.org/wiki/IBM_i#TIMI https://en.wikipedia.org/wiki/IBM_i#TIMI. IBM i is on a POWER CPU today, but can still run System/38 binaries from the 70s, thanks to install-time compilation to whatever CPU the system is running this decade.