There was great excitement and relief when the 80386 came out with its 32bit address linear memory model. Everything suddenly became possible - serious compute on the desktop.
Also remember fondly the workhorse that was the Core2Duo and the i4700k beast, and Mike Abrashes Black book on game programming.
LLM-style AI doesn't yet seem to be the growth technology we need to bring back the economic prosperity of the 80s-90s - but if RL can figure out a stable plasma fusion configuration and layout chips for much better data-flow, then we might see the level of prosperity and innovation we saw in those decades when Moores Law held sway.
I wasn't really in the PC world at the time but I do remember this. I remember the first time using a 386 and feeling that, finally, PCs were genuinely powerful machines capable of genuinely impressive feats of computing.
They removed from the ISA a branch-on-bit instruction and reduced the address size from 16 bits to 14 bits, because at that time Intel could not use bigger integrated circuit packages, with enough pins for a complete address.
Another nitpick: the article says 8085 had multiplexed address/data bus. This is actually also true for 8008, 8080 before it, and 8086, 8088, and 80186/88 after it.
In my opinion, not only 4004 is completely unrelated to 8008 and x86, but it also does not deserve to be called a "microprocessor", which is intended to mean "monolithic computer CPU", while it can be argued that the 4004 chip set was neither monolithic nor usable as a general-purpose computer CPU.
Somebody wrote a MIPS emulator in 4004 and used the emulated system to run linux. (it took a week to boot) I'd argue that if it runs linux it is a general purpose computer CPU.
I agree that it is not monolithic; you can't do anything without the associated ROM+IO chip. But I'd argue that's largely semantics. You can't use a modern x86 CPU without a motherboard full of associated chips either. Although it's not the Platonic ideal of a single monolithic IC, 2 chips to run programs is good enough.
I don't know why Intel and AMD are still doing this.
If they changed their CPUs to start in long mode (or even just 32-bit protected mode), nobody would notice except BIOS writers.
And BIOS writers expect to have to change their code to support new CPUs anyway. If Intel and/or AMD made it an ultimatum, the BIOS vendors would comply.
I know Intel had a plan to remove real mode and 16-bit support entirely, X86S, which they abandoned. But a lot of people opposed that because it would have harmed backward compatibility, including the ability to run older OS versions under virtualisation. Changing the physical CPU to no longer start in real mode would be invisible to everything except the BIOS, and even for the BIOS, only its early initialisation code would have to change.
This isn't like an operating system where backwards compatibility takes effort. Since this sits on the boot path, it takes more effort to remove a wart than to just leave it.
I know us developers like to ask "why not fix the wart", but that wart hurts no one.
https://www.os2museum.com/wp/will-the-real-real-mode-please-...
Only the BIOS init code cares about which mode the BSP starts in
But the OS cares about what mode the APs start in. Most operating systems use INIT-SIPI-SIPI, which starts the APs in real mode.
If an OS uses ACPI 6.4 Multiprocessor Wakeup Mailbox instead, then UEFI does the INIT-SIPI-SIPI on the APs, puts them in 64-bit long mode, then hands that to the OS. However, few bare metal UEFI implementations actually implement it, it is mainly implemented by hypervisors to support confidential VMs.
So, Intel/AMD could make the BSP start in 32-bit protected mode, with minimal BIOS code changes; but the APs would still need to start in 16-bit real mode. They couldn't make the APs start in a different mode until they got everyone to move off INIT-SIPI-SIPI.
Ah I always thought it was for eXtended. But I guess X as a placeholder for either H or L makes sense too.
Then, that night, the ritual was to build the computer and, almost invariably, screw up some detail (like forgetting to switch from 220V to 110V on the back of the PSU) which would lead to hours of troubleshooting and despair, and sometimes a trip back to the fair the following day. Inevitably we'd be visited by success and have a brand new generation computer to play the latest games or get On-Line!
Amazing, and experiences for me that are now in this little floating island of time.
the thought of a recall or a disaster/accident which one is responsible for is terrifying.
edit: the reasoning behind casting a down-vote should be public.
Though that's of course an exaggeration for the chips I'm referring to, but that's how it felt, especially with the language barrier.
> This inverted storage, which was to haunt all processors evolved from the 8008, was a result of compatibility with the Datapoint bit-serial processor.
Am I the only one who thinks little endian is the right way to store things? Other than reading multi-byte numbers in order in hex dumps and things like that, I don’t see much advantage to big endian.
So the number '123' is stored in sequential memory locations: x, x+1, x+2 with a word mark under the '1'.
To add (assembly: A X,Y) e.g. '456' to said number at y, y+1, y+2 (in this case the 4 need NOT have a word mark (but usually does) because a word mark in either field ends the operation) the machine starts at the high-order address -- so it starts at address x+2 and y+2, develops any carry, applies that to x+1 and y+1, adds, and finally moves to the hundreds digit, adding any carry from the tens. (The destination address holds the sum in this case, '456' goes to '579')
Also, to move '123' somewhere, you specify the address of the '3' and the field is moved right-to-left to the destination (decrementing the internal pointer, and stopping when finding a word mark).
So, it more or less was Big Endian, but was still able to use a serial ALU by starting at the highest address!
The only exception is IBM, which used both BE bit and byte numbering. (Bit 0 is the most significant bit, and its value depends on the width of the data in question --- exposing the major disadvantage of BE, i.e. a length-dependent term.)
An old adage I've heard and found useful: "Little endian is Logical; Big endian is Backwards."
Famous last words! Temporary lasts longer than you think.
50/60Hz mains power is one of them, and outside engineering this is how society is built and life evolves. Evolution is less of a master craftsman than a process that grabbed what was available at the time.
I've head this claim a lot but have failed to find any real citation for this being the reason for the choice. Does anyone know of any actual evidence that this was the cause?
The exact quote from the latter source is:
"Several other instructions that had been contemplated were not made available because of the software ramifications and the compatibility constraints they would place on the forthcoming 8086."
[1]: https://retrocomputing.stackexchange.com/questions/8040/whic...
[2]: Intel Microprocessors: 8008-8086 published in IEEE Computer, Vol 13, No. 10, page 46, October 1980