2 ms·
If you're a manufacturer that's going to put the industry through the pain of a new ISA, why not start on a clean slate and wipe out 40 years of preconceptions
by cedws 2y ago
If you're a manufacturer that's going to put the industry through the pain of a new ISA, why not start on a clean slate and wipe out 40 years of preconceptions and mistakes? Why not dare to reimagine? If you rework the foundations you can unlock huge leaps that were previously unimaginable.
Apple could have kept using Intel chips and still had MacBooks flying off the shelves for years to come, but they took a risk by tearing it all up and their product is better than ever. (yes, I am aware Apple did not invent their own ISA.)
- jauntywundrkind 2y ago> that's going to put the industry through the pain of a new ISA, X86s is supposed to radically simplify the pain, get rid of a very arcane ratcheting up of antiquated unused modes. It's supposed to decrease pain. And simplify implementation too. We don't dare to reimagine because it's not clear what ISA would be better or what the wins would really be. Folks like Apple turn to existing ancient instruction sets like ARM rather than reinvent because it works and the ISA doesn't really seem to have that much influence on the core design & performance.
- hakfoo 2y agoThe risk with X86S was that people didn't really know what the corner cases were. I'd assume if you start with a fairly vanilla system, all modern x86-64 code, then yeah it's going to work fine. But I could imagine some of the modes and instructions that might get yeeted could cause unforeseen consequences on more "delicate" software. Obviously this means stuff like "386-only binary applications from 1991" but I'd wonder if some of the weird modes are intentionally triggered by things like copy-protection software to make them less easily reverse-engineered.