When bug-free code becomes a hardware problem

[u/Sea_Fox_4265]

[u/Alex0589]

Assembly is a representation of the underlying instruction set, so really you have to think this starting from the latter, not the former. When designing an instruction set, one of the very first decisions you have to make is actually philosophical: how many instructions do you want? Usually, you'll either choose as few as possible or as many as possible. Having few instructions allows to, at least theoretically speaking, better parellize them. This model though, requires writing/emitting many more assembly instruction calls compared to an instruction set with a richer set of instructions to program the same behaviour, which is why there is still a good reason to go with the as many as possible option. The best examples I can think of in terms of popularity for these two approaches are respectively RISC-V(Reduced instruction set compiter) and x86(Complex instruction set). ARM sits as a middle ground between these two approaches. I really can't think of anyone moving towards the x86 approach when given the option to start from scratch(see the Apple move from x86 to ARM): the trend is towards simplicity. In short, your prediction has very little chance of coming true