jgord 5 hours ago

Learned to program on an 8088 machine with Hercules mono graphics card, first in GW-Basic which was godawful, then in A86 assembler and finally Turbo Pascal which was a pinnacle of human engineering, a portal into a wonderful future ahead.

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.

  • bananaboy 4 hours ago

    I used A86! That was a great little assembler!

  • bartread 4 hours ago

    > 80386 came out with its 32bit address linear memory model. Everything suddenly became possible - serious compute on the desktop.

    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.

chimpontherun 4 hours ago

Cool article, thanks! Nitpick: the reason behind the little endianness _originally_ was data access speed-up on 2200, not arithmetic. The 2200 only had 8-bit arithmetic (as did 8008), but its address bus was processed low-to-high. The arithmetic angle became relevant in 8080, with its 16-bit arithmetic. Side benefit: casting between 8- and 16-bit data using the same 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.

petercooper 10 hours ago

This is a neat history. However, going to be a bit nitpicky since they put this in bold re the 8008: "Intel did not design the instruction set of this chip" .. kinda true in a broad sense, but Intel engineers including Stan Mazor did change and enhance it, like adding increment and decrement operations and some other stuff mentioned in https://archive.computerhistory.org/resources/text/Oral_Hist...

  • adrian_b 9 hours ago

    The increment and decrement instructions were the only enhancements, according to what is said at your link.

    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.

    • wk_end 8 hours ago

      The link describes increment/decrement as “one of the enhancements we made” (emphasis mine). The other things rattled off there aren’t necessarily “enhancements”, so I don’t think it’s clear that Mazor is giving an exhaustive list of changes or enhancements.

kens 10 hours ago

One thing I'd emphasize is that the 4004 is not related to the 8008 at all, except that many of the same people worked on both chips.

  • adrian_b 9 hours ago

    Yes, the only relationship between 4004 and x86 is that the team which designed 4004 practically learned on it how to design PMOS logic circuits and by the end of the project they had a methodology of how to design such logic circuits in a more efficient way, which then they applied in their next project, which became Intel 8008.

    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.

    • nwallin 6 hours ago

      > In my opinion, [...] 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.

gregschlom 7 hours ago

> And what does the "X" mean? According to Morse himself, nothing special. It was simply an arbitrary letter combining the "H" and "L" halves into one 16-bit register (as told to Vladimir Keleshev).

Ah I always thought it was for eXtended. But I guess X as a placeholder for either H or L makes sense too.

skissane 3 hours ago

> why does a modern PC still wake up pretending to be a chip from 1978?

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.

  • colejohnson66 3 hours ago

    Virtualization is a big thing. But it's also just effort. Keeping the cruft in costs nothing - the HDL doesn't change. It works any everyone knows how to deal with it.

    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.

    • skissane 3 hours ago

      Actually, I just learnt something...

      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.

  • BSPtree 3 hours ago

    I would blindly guess... because of legacy reasons?

VolCoder 7 hours ago

I built my first machine using a 80486! It took a lot back then to build a machine. No YouTube, no Discord, no internet (for all intents and purposes). But a heck of a lot of fun!

  • bluedino 7 hours ago

    I had the Que publishing book, Building and Repairing PC's. What a resource.

  • IAmNotACellist 6 hours ago

    Also one had to go to computer fairs when they were in town (or at least, that's what my father and I did), and oftentimes pick out some chip laid out in a wooden box with the clockspeed or details written on it in sharpie. Especially the previous generation, or possibly sketchy third-shifted or engineering units that could be had at a big discount. You'd often have to point to what you wanted, as the vendors were Taiwanese or Chinese, and cash was appreciated or possibly even required.

    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.

    • VolCoder 4 hours ago

      I grew up pretty rural, so we didn't have the fairs. We relied on the old catalogs. Remember Jameco, and the Computer Shopper magazine with all the supplier ads?

      • compiler-guy 3 hours ago

        Jameco is still in business at jameco.com and has a terrific web site for sourcing discrete logic and similar parts. I have built many a breadboard project with materials sourced from there.

    • tosapple 3 hours ago

      i resent the implications of 'third-shifted', to betray my own operational security: i work third shift, enjoy it... and believe i am by far the largest quality hawk at our business outside of upper management.

      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.

drob518 9 hours ago

Talking about little endian…

> 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.

  • hikarudo 9 hours ago

    Me too, little endian makes more sense.

  • dmitrygr 8 hours ago

    Yes. Especially for lower-bit-width chips which must serially do longer-bit-width-math, LE makes sense, since the pieces you work with are in memory in proper order.

  • GeorgeTirebiter 8 hours ago

    The way the IBM 1401 does it, because it's a variable word-length machine (fields being delineated by Word Marks, which is a bit in each core location specifically for marking the end of a field / instruction).

    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!

    • tosapple 3 hours ago

      big-endian is reminiscent of serialization and stack orientation.

  • hyperman1 7 hours ago

    It is our numeric system that is backward. 123 should be written 321. But, Arab is written right to left, and we took their convention when we took their numbers.

BSPtree 3 hours ago

little endianness indeed only makes sense intuitively if the addition is bitwise. Why not fetch all the bytes then feed them into a carry look ahead adder?

RetroTechie 4 hours ago

"This hack lived much longer than anyone expected:"

Famous last words! Temporary lasts longer than you think.

  • RachelF 2 hours ago

    Yes, the world is full of hacks, things done for historical reasons that are no longer valid, but need to be kept to maintain backwards compatibility.

    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.

seblon 10 hours ago

As far as I remember, some chips was called 586 and 686,but I think this was just a synonym for Pentium processors.

  • ido 10 hours ago

    Pentium and Pentium-Pro (also reused i686 for later chips).

  • kens 10 hours ago

    The chips were going to be given those names, but the names were changed to Pentium and Pentium Pro for trademark reasons. Specifically, Intel couldn't trademark the numbers, which allowed competitors to call their chips the same numbers.

    • immibis2 7 hours ago

      It's false by the way - you can trademark numbers, colours, and stuff like that

      • transitorykris 5 hours ago

        Completely true, they were denied the application for lack of distinctiveness. I'm not going to google that for you.

  • epcoa 10 hours ago

    This was never a widespread official Intel designation. Outside of Intel we use 586 and 686 to refer to the Pentium and Pentium Pro, it’s used by GCC, Linux, modern BSDs, etc, but it was never used widely by Intel marketing nor engineering. Intel proactively trademarked all names up to 986/i986 but this was before the AMD lawsuit.

  • nout 9 hours ago

    Cyrix and AMD called those 5x86 and 6x86 (you can find pictures of those chips), because they couldn't call it "Pentium".

qurashee 5 hours ago

Gustavo is an amazing educator, really worth watching some of his courses.

dmitrygr 8 hours ago

> the 8085 had 12 new instructions, but Intel made a last-minute decision to document only 2 of them. The reason? To keep things simple for the next chip, which was already being designed. That chip was the 8086

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?

  • raphlinus 5 hours ago

    A retrocomputing Stack Exchange [1] thread looks like a really good source. That in turn cites [2] with Stephen P Morse, 8086 architect, as first author. I'd consider that pretty authoritative.

    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

walrus01 4 hours ago

I know this article is more about the instruction set, but I'm kind of surprised it entirely skips mentioning the 386SX (and the AMD 386SX), which was wildly popular in the lower end of home computers and some basic laptops for quite a while in the windows 3.0/3.1 era.

mdmizanur0001 9 hours ago

is this a consumer grade CPU or it's a enterprise grade?