3 ms·
The reason it is "unbelievably bad" is because it's not machine-readable. It's a PDF that comes out of FrameMaker for crying out loud. Some parts of it are no
by ebikelaw 8y ago
The reason it is "unbelievably bad" is because it's not machine-readable. It's a PDF that comes out of FrameMaker for crying out loud. Some parts of it are not even human-readable, such as this garbled chart in ORM 3.7.6.1, the otherwise rather confusing description of the possible benefits of REP MOVSB on Ivy Bridge or later, under certain circumstances, maybe.
I mean, the image is just totally unreadable. https://imgur.com/a/jqxpqAf https://imgur.com/a/jqxpqAf
- glangdale 8y agoI agree that it could be improved, but I think "unbelievably bad" is hyperbole. This is especially true in light of comparisons to other vendors; I'm not aware of any up-to-date machine-readable information that's the equivalent for Appendix C for any other vendor, and historically (pre Intel acquisition) we had trouble finding this information out at all for some of our platforms to which we had Hyperscan ports. It was either out of date, not available, or behind a paywall ("show you've bought our SDK to get basic processor docs").