3 ms·
I believe the first "page" of opcodes (i.e. 1-byte opcodes, the ones that don't start with 0F) has already been extensively researched and documented, at least
by userbinator 7y ago
I believe the first "page" of opcodes (i.e. 1-byte opcodes, the ones that don't start with 0F) has already been extensively researched and documented, at least in 16 and 32-bit mode; the interesting things are all in the "second page", the ones that begin with 0F and are relatively new instructions, and the awkward and somewhat inconsistent way in which 64-bit mode was implemented.
Also, the fact that they're trying to test undocumented behaviour from within a full OS was a bit unexpected; in the retrocomputing community, where CPUs like the Z80 and 6502 have been studied extensively, the usual way of testing undocumented behaviour is to boot into a very minimal environment whose only purpose is test that behaviour, so as to eliminate any other variables from the process. Logic analysers/bus monitoring are also used sometimes, although that might be harder with a modern high-speed CPU.
- s_gourichon 7y ago"High speed" shouldn't be a concern, should it? By adjusting the clocks I believe you can run the CPU as slow as you wish. Complexity and the ratio of visible behavior over unobservable state is astronomically worse than for a 8bit CPU and therefore a concern, still.
- userbinator 7y agoDue to things like dynamic logic and PLLs (https://en.wikipedia.org/wiki/Phase-locked_loop https://en.wikipedia.org/wiki/Phase-locked_loop ), modern CPUs can't clock down into the tens of MHz range or lower. There's also the issue of things like DRAM refresh.