this post was submitted on 05 May 2025
16 points (94.4% liked)

retrocomputing

4914 readers
132 users here now

Discussions on vintage and retrocomputing

founded 2 years ago
MODERATORS
top 5 comments
sorted by: hot top controversial new old
[–] PhilipTheBucket@ponder.cat 6 points 1 month ago (1 children)

I knew it, man.

I learned MIPS assembly first, and it was like the registers were all a baseball team, with everyone trained and doing their part to try to get the job done.

When I learned about x86 assembly it was like the registers were a tiny band of wacky misfits who were going around in a van trying to solve mysteries.

  • Code segment: fine
  • Data segment: It's weird that you even do "segments" but fine
  • Extra segment: ...
  • F segment: Please stop
  • G segment: Stop it
[–] paulh@lemmy.sdf.org 4 points 1 month ago

Fantastic description!

Z-80 was much the same: djnz uses C as the loop counter (like the 8086 LOOP used CX iirc), H and L combine to make a 16-bit pointer...

[–] hbm 1 points 1 month ago

The fact that x86. Hasn’t changed its foundation much, isn’t that just a combination of hardware making up for original design shortcomings, while economy keeping better solutions at bay? (Not a chip guy, I’m likely wrong.)

[–] hbm 1 points 1 month ago

Never did SPARC assembly, but ISTR their registers were basically a ring of groups of registers allowing fast context switches as long as the call depth stayed shallow (fsvo shallow). When the ring was exhausted, you had to stash away in memory.

[–] ThorrJo@lemmy.sdf.org 1 points 1 month ago

Ken Shirriff regularly posts cool hardware deep-dives and can be followed on fedi at @kenshirriff@oldbytes.space