3 ms·
If you have the source code to all your software, generally speaking open source (although proprietary software occasionally comes with source code included), a
by skissane 10y ago
If you have the source code to all your software, generally speaking open source (although proprietary software occasionally comes with source code included), and you know how to build it, then removing old instructions from an ISA is feasible. Once the compiler is modified/reconfigured to not emit the removed instruction any more, just recompile everything.
If all your code is bytecode running on a VM (such as Java or .Net bytecode), then you don't even need the source to your applications – just make sure the VM's JIT compiler is not emitting the old instruction any more.
A good example of the later was the IBM AS/400. The high-level languages in which applications were written – COBOL, RPG, PL/I, etc – all compiled to an intermediate bytecode (MI code). The original AS/400s used a proprietary CISC CPU, whose instruction set was never publicly documented by IBM, although I've heard it was inspired by the System/370 mainframe instruction set. The OS would translate MI bytecode (which was documented to customers) into the underlying CISC instructions. Later, when IBM moved the AS/400s to PowerPC, they just had to replace the MI-to-CISC translator with an MI-to-PowerPC translator, and all that old code just worked. (I simplify somewhat – they also rewrote most of the lower-level OS code from a PL/I dialect into C++ – although, that was more of a good idea than something strictly required by the CISC-to-PowerPC migration.)
By contrast, it is very hard for Intel to drop anything from x86, even rarely used features (e.g. BCD arithmetic instructions), because somewhere out there someone has a business critical closed source app which uses that feature, and the source code for it might not even exist any more.
So, at least in principle, an open source ISA could actually drop things faster than many proprietary ISAs do. It really depends on what kind of software ecosystem ends up running on that ISA.
- Nomentatus 10y agoNot to contradict others messages here, but to add to them: the argument (made elsewhere) by RISC-V peeps is that Intel etc regularly introduce rather junky instructions that they can and do patent (the mechanism of), merely in order to continue to patent encumber the collective ISA, and so keep the network effect as their purely proprietary possession, long after the truly significant patents have lapsed; since compatibility would now require the new instructions, too. I'm not making that argument, although it may well be correct, I'm pointing to it.
- pjmlp 10y agoAs an addendum to your list for the other readers, C, C++ and Java AS/400 compilers can also generate MI code. Also Microsoft already had it for Windows CE, it was called Common Executable Format for eMbedded short CEF. https://msdn.microsoft.com/en-us/library/ms834338.aspx https://msdn.microsoft.com/en-us/library/ms834338.aspx Processor independence is also a reason why mobile OSes are going into this direction.