3 ms·
I think it's technically seven now, though I know of no one with a paper copy. My not-quite-current PDF copy of the SDM splits its 3289 pages into three volume
by ajross 11y ago
I think it's technically seven now, though I know of no one with a paper copy. My not-quite-current PDF copy of the SDM splits its 3289 pages into three volumes, with volumes 2 and 3 being split into A, B and C subvolumes.
And yes, virtually everything remains compatible. So if you want to write a 32 bit code generator and don't need access to newer features (synchronization primitives are the most important bits that were added later, also stuff like vector instructions, etc...) that 30-year-old document is all you need.
- justwannasing 11y agoI have paper copies going back to the mid 80s.
- cbd1984 11y agoIf you limit yourself to the 16-bit subset, you can use manuals that are even older. And if you give up binary portability and restrict yourself to the source portability which helped sell people on the 8086 and the 8088 to begin with, you can use a manual for an 8080 processor and convert the code to the earliest 16-bit subset, prior to the expansions the 80286 brought. And if that's too recent for you, you can move to the IBM mainframe series derived from the System/360 architecture, and use layer upon layer of emulation to run software written in the Johnson administration. Screw diamonds: Legacy systems are forever.
- raverbashing 11y agoYes, you can stick to 16-bit and keep using 640k of RAM, segments and offsets No, thank you