From C64-Wiki
Jump to navigationJump to search

BCS (short for "Branch if Carry is Set") is the mnemonic for a machine language instruction which branches, or "jumps", to the address specified if, and only if the carry flag is set. If the carry flag is clear when the CPU encounters a BCS instruction, the CPU will continue at the instruction following the BCS rather than taking the jump.

BCS in comparisons[edit]

Main article: Comparisons in machine language

BCC and its "counterpart", BCS, are often used after a "compare" instruction (either CMP, CPX, or CPY) in conjunction with comparing unsigned 8-bit integers, like e.g.:

LDA NumA    Read the value "NumA"
CMP NumB    Compare against "NumB"
BCS Larger  Go to label "Larger" if "NumA" >= "NumB"
...         Execution continues here if "NumA" < "NumB"

For signed integers, this method fails if NumA and NumB have different arithmetic signs (i.e. one negative, the other positive) — instead, BPL and BMI should be used for greater than/less than-style comparisons of signed bytes.

Addressing mode[edit]

Opcode Addressing
in bytes
Number of
Dec Hex
176 B0 Relative BCS nn 2 2*

BCS only supports the Relative addressing mode, as shown in the table at right. In the assembler formats listed, nn is a one-byte (8-bit) relative address. The relative address is treated as a signed byte; that is, it shifts program execution to a location within a number of bytes ranging from -128 to 127, relative to the address of the instruction following the branch instruction.
The execution time for BCS is not a fixed value, but depends on the circumstances. The listed time is valid only in cases where BCS does not take the branch. If it does take the branch, execution takes one additional clock cycle. Furthermore, if the branching crosses a page boundary, yet another cycle must be added to the execution time listed.

CPU flags[edit]

BCS does not affect neither the carry flag or any other CPU's status flag.