KIM-1

@kim-6502.bsky.social did:plc:bvov6bptqbqdupr7m4khwwug

The KIM-1 and classic 6502 related topics. Zero page FTW!

No Bluesky desde 14 janeiro 2025

Resumo

KIM-1 (@kim-6502.bsky.social) é um usuário do Bluesky desde 14 janeiro 2025. Tem 657 seguidores, segue 1.070 contas e publicou 925 posts.

Os melhores dias em que posts desta conta entraram na lista diária do Debya.

Esta conta ainda não apareceu em um ranking diário.

Curtidas públicas da rede Bluesky.

Simon Harris@simondo65.bsky.social02/11/2026 15:38
Yes, quite often if you knew a particular calculation would always yield a constant condition code value (e.g. an addition that could never overflow), you could arrange your code to place it just before the branch, and substitute an appropriate conditional branch for the non-existent BRA.
Ver post
Vin 😺💜@vinscool.bsky.social02/11/2026 14:26
I love the unconditional branches to save few cycles and bytes.
Ver post
Simon Harris@simondo65.bsky.social02/11/2026 14:26
Bxx +0 (where xx is one of the conditions EQ, NE, CC, CS, etc) just branches to the next instruction, so effectively does nothing. But untaken branches are 2 cycles, taken are 3 (4 if a page is crossed) Are there any real-world examples of where Bxx +0 was used as a programmable length NOP?
Ver post
bflmouse.bsky.social@bflmouse.bsky.social02/11/2026 14:26
Been there, done that. It's not fun. You _can_ use a zero in the code hidden in a REM statement. It just has to be the last byte in that statement, and you cannot use the following five bytes for anything, so the zero has to be data, not part of an instruction.
Ver post
Vin 😺💜@vinscool.bsky.social02/11/2026 14:26
Yes, the BRA instruction, what I meant to say was simply using the cleverly programmed branches that were guaranteed to always be taken, which effectively provided the same outcome. eg: Carry Set before branching, Overflow Clear, etc.
Ver post

No Bluesky, bloqueios são registros públicos.