> 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.
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...
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.
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.
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!
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.
> 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.
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!
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.
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.
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.
> 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 head this claim a lot but have failed to find any real citation for this being the reason for the choice. Does anyone know if any actual evidence that this was the cause?
Ah I always thought it was for eXtended. But I guess X as a placeholder for either H or L makes sense too.
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.
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.
> 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!
I head this claim a lot but have failed to find any real citation for this being the reason for the choice. Does anyone know if any actual evidence that this was the cause?