This old paper tells the history of early Intel CPUs and discusses their features and major design decisions: the 8008, 8080, 8085, and 8086. The paper provides interesting technical and historical tidbits, such as the reason why the 8008 was little endian and hence later CPUs.
This is a demake of Geometry Wars, which is a twin stick shooter - you may have noticed that the Gameboy does not have twin sticks. ➕ 🔴🔴
But I have some ideas for that to try out, either before or after I make the first enemies. I'm starting to get the hang of the hardware and thinking in assembly now, and I have more reusable functions. Progress!
Felt just a bit sad about this news. The #Z80 was the second microprocessor that I ever coded #assembly on after the Intel x86. I remember burning an EPROM with a Z80 program that controlled the brightness level of an LED in one of my early practical microprocessor exercises in college.
After the kids are in bed I might get two hours where I have the brain function to get stuck into assembly coding. When I hit a problem bigger than two hours I get stuck for a while. This was the case moving specific movement and render code I wrote for the player to be more generic for entities including bullets and enemies. Now I'm unstuck this is looking more like a game.
I'm trying to fix a patch to allow #pixman's #ARM#NEON#assembly code to build with clang. They perform a lot of mechanical changes to switch to the "unified" ARM assembly syntax (.syntax unified), supported by both #gcc and #clang.
With clang the code builds but fails 3 of the tests in the test suite with what appear to be unaligned accesses. With gcc, the test suite passes before and after the patches.