CPU status flag behavior: Difference between revisions
m (→The B flag: "if from an interrupt" might have objections among people who use the term "software interrupt") |
(P bit chart: don't imply that V from BIT is inverted or that bit 3 likewise don exits) |
||
Line 12: | Line 12: | ||
|| +---- D: 1 to make ADC and SBC use binary-coded decimal arithmetic | || +---- D: 1 to make ADC and SBC use binary-coded decimal arithmetic | ||
|| (ignored on second-source 6502 like that in the NES) | || (ignored on second-source 6502 like that in the NES) | ||
|+-------- V: 1 if last ADC or SBC resulted in signed overflow, | |+-------- V: 1 if last ADC or SBC resulted in signed overflow, | ||
| D6 from last BIT | | or D6 from last BIT | ||
+--------- N: Set to bit 7 of the last operation | +--------- N: Set to bit 7 of the last operation | ||
</pre> | </pre> | ||
Line 39: | Line 39: | ||
The slowness of this is one reason why BRK wasn't used as a syscall mechanism. | The slowness of this is one reason why BRK wasn't used as a syscall mechanism. | ||
Instead, it was more often used to trigger a patching mechanism that hung off the /IRQ vector: a single byte in PROM, UVEPROM, flash, etc. would be forced to 0, and the IRQ handler would pick something to do instead based on the program counter. | Instead, it was more often used to trigger a patching mechanism that hung off the /IRQ vector: a single byte in PROM, UVEPROM, flash, etc. would be forced to 0, and the IRQ handler would pick something to do instead based on the program counter. | ||
Unlike bits 5 and 4, bit 3 actually exists in P, even though it doesn't affect the ALU operation on the 2A03 or 2A07 CPU the way it does in MOS Technology's own chips. | |||
== External links == | == External links == | ||
*[http://nesdev.parodius.com/bbs/viewtopic.php?p=64224#64224 koitsu's explanation] | *[http://nesdev.parodius.com/bbs/viewtopic.php?p=64224#64224 koitsu's explanation] |
Revision as of 05:17, 30 August 2010
The flags register, also called processor status or just P, is one of the six architectural registers on the 6502 family CPU.
There are six bits in P:
7654 3210 || |||| || |||+- C: 1 if last addition or shift resulted in a carry, or if || ||| last subtraction resulted in || ||+-- Z: 1 if last operation resulted in a 0 value || |+--- I: Interrupt priority level || | (0: /IRQ and /NMI get through; 1: only /NMI gets through) || +---- D: 1 to make ADC and SBC use binary-coded decimal arithmetic || (ignored on second-source 6502 like that in the NES) |+-------- V: 1 if last ADC or SBC resulted in signed overflow, | or D6 from last BIT +--------- N: Set to bit 7 of the last operation
The B flag
There are six and only six flags in the processor status register. Despite what some 6502 references might appear to claim on a first reading, there is no "B flag" in the CPU.
Two interrupts (/IRQ and /NMI) and two instructions (PHP and BRK) push the flags to the stack. Bit 5 is always set to 1, and bit 4 is 1 if from an instruction (PHP or BRK) or 0 if from an interrupt line being pulled low (/IRQ or /NMI).
Instruction | Bits 5 and 4 | Side effects after pushing |
---|---|---|
PHP | 11 | None |
BRK | 11 | I is set to 1 |
/IRQ | 10 | I is set to 1 |
/NMI | 10 | I is set to 1 |
Two instructions (PLP and RTI) pull a byte from the stack and set flags. They ignore bits 5 and 4.
The only way for an IRQ handler to distinguish /IRQ from BRK is to read the flags from the stack and test bit 4. The slowness of this is one reason why BRK wasn't used as a syscall mechanism. Instead, it was more often used to trigger a patching mechanism that hung off the /IRQ vector: a single byte in PROM, UVEPROM, flash, etc. would be forced to 0, and the IRQ handler would pick something to do instead based on the program counter.
Unlike bits 5 and 4, bit 3 actually exists in P, even though it doesn't affect the ALU operation on the 2A03 or 2A07 CPU the way it does in MOS Technology's own chips.