Intel: from 8086 to 80486 - an emotional story
Of course, one of the best processors made in the 70's is the 8086, and also its cheaper almost analogue 8088. The architecture of these processors is pleasantly distinguished by the absence of mechanical borrowings and adherence to abstract theories, the thoughtfulness and balance of architecture, steadiness and focus on further development. Of the drawbacks of the architecture of x86, you can call it a bit cumbersome and prone to an extensive increase in the number of instructions.
One of the brilliant constructive solutions of the 8086 was the invention of segment registers. This, as it were, simultaneously achieved two goals – the "free" ability to relocate codes of programs, up to 64 KB in size (this was even a decent amount for computer memory for one program up to the mid-80's), and addressability up to 1 MB of address space. You can also notice that the 8086, like the 8080 or z80, also has a special address space for 64 KB I/O ports (this is 256 bytes for the 8080 and 8085). Segment registers are only four: for the code, for the stack, and two for the data. Thus, 64 * 4 = 256 KB of memory is available for quick use, but it was very much even in the mid-80's. In fact, there is no problem with the size of the code, since it is possible to use long subroutine calls with loading and storing a full address from two registers. There is only a limit of 64 KB for the size of one subroutine – this is enough even for many modern applications. Some problem is created by the impossibility of fast addressing to data arrays larger than 64 KB - when using such arrays, it is necessary to load a segment register and the address itself with each access, which reduces the speed of work with such large arrays several times.
Segment registers are implemented in such a way that their presence is almost invisible in the machine codes, so, when time had come, it was easy to abandon them.
The architecture of the 8086 retained its proximity to the architecture of the 8080, which allowed relatively small efforts to transfer programs from 8080 to 8086, and especially if the source code was available.
The 8086's instructions are not very fast, but they are comparable to competitors, for example, the Motorola 68000, which appeared a year later. One of the innovations, some accelerating rather slow 8086, became instructions queue.
8086 uses eight 16-bit general purpose registers, some of which can be used as two one-byte registers, and some as index registers. Thus, the 8086 registers characterize some heterogeneity, but it is well balanced and the registers are very convenient to use. This heterogeneity, by the way, allows having more dense codes. 8086 uses the same flags as the 8080, plus a few new ones. For example, a flag appeared typical for the architecture of PDP-11 – step-by-step execution.
8086 allows you to use very interesting addressing modes, for example, the address can be made up of a sum of two registers and a constant 16-bit offset, on which the value of one of the segment registers is superimposed. From the amount that makes up the address, you can leave only two or even one summand. Such on the PDP-11 by one command will not turn out. Most commands in the 8086 do not allow both operands of memory type, one of the operands must be a register. But there are string commands that just know how to work with memory using addresses. String commands allow you to do quick block copying (17 cycles per byte or word), search, fill, load and compare. In addition, string commands can be used when working with I/O ports. Very interesting is the idea of using the 8086 instruction prefixes, allowing to use often very useful additional functionality without significantly complicating the encoding schemes of CPU instructions.
8086 has one of the best design of work with the stack among all computer systems. Using only two registers (BP and SP), the 8086 allows solving all problems when organizing subroutine calls with parameters.
Among the commands there are signed and unsigned multiplication and division. There are even unique commands for decimal corrections for multiplication and division instructions. It's hard to say that in the 8086 command system, something is clearly missing. Quite the contrary. The division of a 32-bit dividend into a 16-bit divisor to obtain a 32-bit quotient and 16-bit remainder may require up to 300 clock cycles - not particularly fast, but several times faster than such a division on any 8-bit processors (except 6309) and is comparable in speed with 68000. The division in x86 has one unexpected feature - it corrupts all arithmetic flags.
It's worth adding that in the x86 architecture, the XCHG command inherited from the 8080 has been improved. In addition, the later processors began to use instructions XADD, CMPXCHG and CMPXCHG8B, which can also perform atomic exchange of arguments. Such instructions are one of the features of x86, they are difficult to meet on the processors of other architectures.
It can be summarized that 8086 is a very good processor, which combines the ease of programming and attachment to the limitations on the amount of memory of that time. 8086 was used comparatively rarely, giving way to a cheaper 8088 honorable place to be the first processor for the mainstream PC for the personal computers of our time. 8088 used 8-digit data bus what did him somewhat slower, but allowed to build systems on its base more accessible to the customers.
80186 and 80286 appeared in 1982. Thus, it can be assumed that Intel had two almost independent development teams. 80186 is 8086 improved by several commands and shortened timings plus several chips integrated into the chip typical of the x86 architecture: a clock generator, timers, DMA, interrupt controller, delay generator, etc. Such a processor could greatly simplify the production of computers based on it, but due to some unclear reason it is almost never used in the PC. The author knows only the BBC Master 512 based on the BBC Micro computer, which did not use built-in circuits, even a timer, but there were several other systems using 80186. Addressed memory with 80186 remained as with 8086 sizes in 1 МБ.
80286 had even better timings than 80186, among which stands out just a fantastic division (32/16=16,16) for 22 clock cycles - since then they have not learned how to do the division faster! 80286 supports working with all new instructions of 80186 plus many instructions for working in a new, protected mode. 80286 became the first processor with built-in support for protected mode, which allowed to organize memory protection, proper use of privileged instructions and access to virtual memory. Although the new mode created many problems (the protected mode was rather unsuccessful) and was relatively rarely used, it was a big breakthrough. In this new mode, segment registers have acquired a new quality, allowing up to 16 MB of addressable memory and up to 1 GB of virtual memory per task. The big problem with 80286 was the inability to switch from the protected mode to real mode, in which most programs worked. Using the "secret" undocumented instruction LOADALL, it was possible to use 16 MB of memory being in the real mode.
In 80286, the calculation of an address in an instruction operand became a separate scheme and stopped slowing down the execution of commands. This added interesting features, for example, with the command
LEA AX,[BX + SI + 4000] in just 3 cycles it became possible to perform two additions and transfer the result to the AX register!
The number of manufacturers and specific systems using 80286 is huge, but, indeed, the first computers were IBM PC AT with almost fantastic personal computer performance indicators for speed. With these computers, memory began to lag behind the speed of the processor, wait states appeared, but then it seemed still something temporary.
Protected mode of 80286 was extremely inconvenient, divided all memory into segments of no more than 64 KB and required complicated software support for working with virtual memory. 80386, appeared in 1985, made the work in the protected mode quite comfortable, allowed to use up to 4 GB of addressable memory and easily switch between modes. In addition, to support multitasking for programs for the 8086, the virtual 8086 mode was made. For virtual memory, it became possible to use a relatively easy-to-manage page mode. 80386 for all its innovations has remained fully compatible with the programs written for the 80286. Among the innovations of 80386, you can also find the extension of registers to 32-bits and the addition of two new segment registers. The timings have changed, but ambiguously. A barrel shifter was added, which allowed multiple shifts with timings of one. However, this innovation for some reason very slowed down the execution of the commands of cyclic rotates. The multiplication became slightly slower than that of 80286. Working with memory became, on the contrary, a little faster, but this does not apply to string commands that stayed faster for 80286. The author of this material has often had to come across the view that in real mode with 16-bit code 80286 in the end is still a little bit faster.
Several new instructions were added to 80386, most of which just gave new ways for work with data, actually duplicating with optimization some already present instructions. For example, the following commands were added:
* to check, set and reset a bit by number, similar to those that were made for z80;
* bit-scan BSF and BSR;
* copy a value with a signed or zero bit extension, MOVSX and MOVZX;
* setting a value depending on the values of operation flags by SETxx ;
* shifts of double values by SHLD, SHRD.
X86 processors before the appearance of 80386 could use only short, with an offset of one-byte conditional jumps – this was often not enough. With 80386 it became possible to use offset of two or four bytes, and despite the fact that the code of new jumps became two or three times longer, the time of its execution remained the same as in previous, short jumps.
The support for debugging was radically improved by the introduction of 4 hardware breakpoints, using them, it became possible to stop programs even on memory addresses that may not be changed.
The protected mode became much easier to manage than in 80286, which made a number of inherited commands unnecessary rudiments. In the main protected, so-called flat-mode, segments up to 4 GB in size are used, which turns all segmented registers into an unobtrusive formality. A semi-documented unreal mode allowed even to use all the memory as in flat-mode, but from easy to install and control the real mode.
Since 80386, Intel has refused to share its technology, becoming in fact the monopoly processor manufacturer for IBM PC architecture, and with the weakening of Motorola's positions, and for other personal computer architectures. Systems based on the 80386 were very expensive until the early 90's, when they became finally available to mass consumers at frequencies from 25 to 40 MHz. Since 80386 IBM began to lose its position as a leading manufacturer of IBM PC compatible computers. This was manifested, in particular, in that the first PC based on 80386 was in 1986 a computer made by Compaq.
It's hard not to hold back admiration for the volume of work that was done by the creators of the 80386 and its results. I dare even suggest that 80386 contains more achievements than all the technological achievements of mankind before 1970, and maybe even until 1980.
Quite interesting is the topic of errors in 80386. I will write about two. The first chips had some instructions, which then disappeared from the manuals for this processor and stopped executing on later chips. It's about the instructions of IBTS and XBTS. All 80386DX/SXs produced by both AMD and Intel (which reveals their curious internal identity) have a very strange and unpleasant bug that manifested itself in destroying the value of the EAX register if, after writing to the stack or unloading from there all registers with POPAD or PUSHAD used a command that used the address with the BX register. In some situations, the processor could even hang. Just a nightmare bug and very massive, but in Wikipedia, there is still not even a mention of it. There were other bugs, indeed.
The emergence of ARM changed the situation in the world of computer technology. Despite the problems, the ARM processors continued their development. The answer of Intel was 80486. In the struggle for speed and for the first place in the world of advanced technologies Intel even took a decision to use a cooling fan that spoils the look of the PC till present time.
In 80486, timings for most instructions were improved and some of them began to be executed as on ARM processors during one clock. Although the multiplication and division for some reason became slightly slower. There is quite a big built-in cache memory for those years, with the size of 8 KB. There were also new instructions, for example, CMPXCHG – it took the place of the imperceptibly missing instructions of IBTS and XBTS (interesting, as a secret this instruction was available already at the late 80386). There are very few new instructions - only six, of which it is worth mentioning a very useful instruction for changing the order of bytes in the 32-bit word BSWAP. A big useful innovation was the presence of a built-in arithmetic coprocessor chip - so no one else did.
The first systems based on the 80486 were incredibly expensive. Quite unusual is that the first computers based on 80486, the VX FT model, were made by the English firm Apricot - their price in 1989 was from 18 to 40 thousand dollars, and the weight of the system unit is over 60 kg! IBM released the first computer based on 80486 in 1990, it was a PS/2 model 90 with a cost of $17,000.
It's hard to imagine the Intel processors without secret, undocumented officially features. Some of these features have been hidden from users since the very first 8086. For example, such an albeit useless fact that the second byte in the instructions of the decimal correction of AAD and AAM matters and can be different, generally non-decimal (it was documented only for the Pentium processor after 15 years!). It is more unpleasant to silence the shortened AND/OR/XOR instructions with an operand byte constant, for example, AND BX, 7 with an opcode of three bytes length (83 E3 07). These commands, making the code more compact, which was especially important with the first PCs, were quietly inserted into the documentation only for 80386. It is interesting that the Intel's manuals for 8086 or 80286 have a hint about these commands, but there are no specific opcodes for them. Unlike similar instructions ADD/ADC/SBB/SUB, for which the full information was provided. This, in particular, led to the fact that many assemblers (all?) could not produce shorter codes. Another group of secrets may be called some strange thing – a number of instructions have two codes of operations. It is, for example, the instructions SAL/SHL (opcodes D0 E0, D0 F0 or D1 E0, D1 F0). Usually, and maybe always, only the first operation code is used. Second, the secret is used almost never. One can only wonder why Intel so carefully preserves these superfluous, cluttering space of opcodes duplicating instructions? The SALC instruction waited for its official documentation until 1995 almost 20 years! Instruction for debugging ICEBP was officially non-existent for 10 years from 1985 to 1995. Most of all, it was written about the secret instructions LOADALL and LOADALLD – they will remain forever secret, as they could be used for easy access to large memory sizes only on 80286 and 80386 respectively. Until recently, there was an intrigue around the UD1 (0F B9) instruction, which was unofficially an example of an incorrect opcode. The informal has recently become official.
In the USSR, the production of clones of processors 8088 and 8086 was mastered, but it could not fully reproduce 80286.
It is a copy of https://litwr.livejournal.com/436.html