10 ms·
I see no real benefit to this. The x86 compatibility doesn't get in the way in any modern architecture - all the 16/32 bit mode stuff is all 'emulated' with m
by londons_explore 3y ago
I see no real benefit to this. The x86 compatibility doesn't get in the way in any modern architecture - all the 16/32 bit mode stuff is all 'emulated' with microcode, and there are no dedicated 16 bit registers anymore...
Nor does it get in the way of software - as soon as you've switched to 64 bit mode, you can ignore all legacy stuff.
Thats the right way to maintain legacy compatibility - make sure it is all contained and doesn't get in anyone's way, and you can leave it there forever.
- wmf 3y agoThe proposal is from Intel. How sure are we that we know better than Intel?
- moffkalast 3y agoWe ask AMD what they think about it?
- rowanG077 3y agoWhy would Intel propose it if there are is no benefit?
- chx 3y ago1. The neutral answer: to decrease validation costs. 2. The nefarious answer: maybe they found a way in their agreements with AMD which would exclude this X86S somehow.
- mappu 3y agoThe main x86_64 patents have all expired, but this would get to be patented again.
- anticensor 3y agoYou cannot patent a removal without an accompanying addition.
- anticensor 3y ago3. The "Moore's law is dead, long live Wirth's law" answer: They want to increase the clocks, but timings are so tight that they need to remove circuitry and delete bits of microcode to increase it further.
- fwsgonzo 3y agoCan't help but agree. I especially don't like removing ring3 I/O port access. It was/is the fastest way to trap out of a VM without SYSCALL or some other mechanism that I could measure. Segmentation also has its uses, and it's a shame that they are steadily removing it. Having a way to set up a 1:1 memory range without even touching the page tables has always been faster than messing with pages. Indeed, it's always been more performance to either have a fully static page table or just disable it completely and run in 32-bit mode. For certain tasks, it's still the fastest. But these are all niche uses. These days, who thinks about anything other than Windows and Linux use cases? To me though, AMD64 made most problems go away, and the architecture is just fine. Perhaps they want to do away with many of the now rarely used instructions?
- dspillett 3y ago> as soon as you've switched to 64 bit mode, you can ignore all legacy stuff. That, I assume, is the point. If it isn't used by the vast majority why spend the silicon keeping it present? > all the 16/32 bit mode stuff is all 'emulated' with microcode That microcode still needs to be maintained, tested, & verified, with each chip iteration, so it is more than just a tiny bit of silicon that could be repurposed. > and you can leave it there forever If it is there it will be expected to work (otherwise why keep it?) and they need to keep verifying that containment. I'm not much of a hardware guy myself so maybe the risk profile is different - but I've tripped over, or been mugged by, so-called dead code that ends up having “interesting” side effects, enough times for me to not want a bunch of it in my CPU's design if it is avoidable. Removing it has costs somewhere of course, both in Intel's design work and potential compatibility issues in minority use cases. But deciding to leave it in has costs elsewhere, so the options & risks need to be looked into in either case.