3 ms·
One of the crimes propagated from that issue was, Intel deliberately crippled the data-move instruction because folks who shipped lots of software (OK Microsoft
by JoeAltmaier 7y ago
One of the crimes propagated from that issue was, Intel deliberately crippled the data-move instruction because folks who shipped lots of software (OK Microsoft) used it for timing. So as CPUs increased by an order of magnitude, the one-byte ultra-fast data move opcodes become the slowest way to move data. A crime against humanity.
For this reason I'd asked Intel (as a senior programmer at one of Intel's largest CPU chip consumers) for a fixed-rate timer register when they made the 386 e.g. 1MHz free-running counter regardless of CPU speed. While they did implement other requested features (breakpoint registers) somebody screwed up the timer feature and made it full-clock-speed and accessible only thru a privileged instruction. Thus useless for applications.