6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-12-03 05:49:48 +00:00
Code Issues Projects Releases Wiki Activity
74ab1c8137
6502bench/SourceGen/SGTestData/Expected/10032-flags-and-branches_cc65.S

287 lines
4.6 KiB
ArmAsm
Raw Normal View History

Initial file commit
2018-09-28 17:05:11 +00:00
.setcpu "65816"
Attempt to generate segment names for cc65 This worked, sort of. The problem is that SourceGen will revert to hex output in certain situations, such as a broken symbolic reference. There happens to be one in the ZIPPY example, and it's on a relative branch. The goal with the segment stuff is to allow cc65 to treat the source as relocatable code. In that context, a relative branch to an absolute address doesn't make any sense, so the assembler reports a range error. We don't currently have a mechanism that guarantees no references are broken (and no affordance for finding them), so we can't make this mode the default yet. Instead, we continue to use the generic config, but generate the correct set of lines as comments. (issue #39)
2018-11-18 22:36:03 +00:00
; .segment "SEG000"
Initial file commit
2018-09-28 17:05:11 +00:00
.org $1000
.a8
.i8
clc
xce
sep #$ff
clv
cld
cli
clc
lda #$80
lda #$01
sed
sei
sec
lda #$ff
adc #$00
sep #$ff
rep #$80
rep #$40
rep #$20
.a16
rep #$10
.i16
rep #$08
rep #$04
rep #$02
rep #$01
sep #$00
sep #$ff
.a8
.i8
rep #$00
rep #$ff
.a16
.i16
lda #$feed
sec
xce
.a8
.i8
lda #$ff
rep #$30
lda #$ff
clc
xce
lda #$ff
rep #$20
.a16
sep #$10
lda #$0000
ldx #$01
ldy #$02
sep #$20
.a8
rep #$10
.i16
lda #$01
ldx #$0000
ldy #$0000
sep #$30
.i8
lda #$00
pha
plp
rep #$80
bpl L105F
.byte $00
.byte $00
L105F: sep #$80
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
bpl @L1065
bmi @L1067
Initial file commit
2018-09-28 17:05:11 +00:00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1065: .byte $00
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1067: rep #$40
bvc @L106D
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L106D: sep #$40
bvs @L1073
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1073: rep #$01
bcc @L1079
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1079: sep #$01
bcs @L107F
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L107F: rep #$02
bne @L1085
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1085: sep #$02
beq @L108B
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L108B: sep #$ff
Initial file commit
2018-09-28 17:05:11 +00:00
lda #$01
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
bne @L1093
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1093: lda #$00
beq @L1099
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L1099: bpl @L109D
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L109D: lda #$80
bmi @L10A3
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L10A3: lda #$ff
Initial file commit
2018-09-28 17:05:11 +00:00
and #$00
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
beq @L10AB
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Finish removal of "disable label localizer" feature The label localizer is now always on. The regression tests turned it off by default, but that's no longer allowed, so the generated output has changed for many of them. The tests themselves were not altered.
2019-11-17 01:15:03 +00:00
@L10AB: lda #$00
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
ldx #$80
Initial file commit
2018-09-28 17:05:11 +00:00
and #$ff
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
beq @L10B5
bne @L10B5
@L10B5: lda #$ff
ldx #$00
and #$7f
beq @L10BF
bne @L10BF
@L10BF: bpl @L10C3
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10C3: lda #$ff
and #$80
bmi @L10CB
Fix ANDImm flag updater For nonzero values we were leaving Z=prev, which is wrong when Z=0 because the AND result might be zero. Now if Z=1 we leave it alone, but if Z=0 we now set it to Z=?. Test 1003-flags-and-branches was testing for the (incorrect) behavior, so we're now running into a BRK. This is fine.
2020-02-02 00:24:14 +00:00
brk
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10CB: lda #$00
ldx #$80
bne @L10D3
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10D3: ora #$00
beq @L10D9
bne @L10D9
Initial file commit
2018-09-28 17:05:11 +00:00
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10D9: ora #$01
bne @L10DF
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10DF: lda #$00
ldx #$80
bmi @L10E7
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10E7: ora #$7f
bpl @L10EF
bmi @L10EF
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10EF: ora #$80
bmi @L10F5
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
.byte $db
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10F5: lda @L10F5
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
sec
ror A
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
bmi @L10FE
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
.byte $00
.byte $dc
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L10FE: clc
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
ror A
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
bpl @L1104
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
.byte $00
.byte $dc
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L1104: lda #$00
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
sec
rol A
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
bne @L110C
Add custom flag updaters for ROL/ROR There are some useful interactions between C/N and maybe Z. Added a quick test to 1003-flags-and-branches. Also, updated the 2008-address-changes tests. Change b37d3dba extended the nearby-target range of out-of-file symbols by one, so one line that didn't get an operand label now does.
2018-10-09 19:27:47 +00:00
.byte $00
.byte $dc
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L110C: lda #$ff
Recognize that LSR always clears the 'N' flag The instruction shifts 0 into the high bit, so the result is never negative. Added a test case to 1003-flags-and-branches.
2020-04-24 00:23:12 +00:00
lsr A
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
bpl @L1113
Recognize that LSR always clears the 'N' flag The instruction shifts 0 into the high bit, so the result is never negative. Added a test case to 1003-flags-and-branches.
2020-04-24 00:23:12 +00:00
.byte $00
.byte $dd
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L1113: clc
Initial file commit
2018-09-28 17:05:11 +00:00
php
sec
plp
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
bcc @L111B
Update expected results for 10032-flags-and-branches The "smart PLP" behavior change in 2a65457e altered the analysis.
2020-07-30 23:57:33 +00:00
brk
Initial file commit
2018-09-28 17:05:11 +00:00
.byte $00
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L111B: sec
bcs @L111F
Fix code tracing bug If you set things up just right, it's possible for flag status changes to fail to get merged. Added a regression test to 1003-flags-and-branches. Also, tweaked the instruction operand editor to be a bit smoother from the keyboard: added alt-key shortcuts, and put the focus on the OK button after creating/editing a label so you can just hit the return key twice.
2019-09-17 21:38:16 +00:00
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L111E: clc
@L111F: lda $33
beq @L111E
bcs @L1127
Fix code tracing bug If you set things up just right, it's possible for flag status changes to fail to get merged. Added a regression test to 1003-flags-and-branches. Also, tweaked the instruction operand editor to be a bit smoother from the keyboard: added alt-key shortcuts, and put the focus on the OK button after creating/editing a label so you can just hit the return key twice.
2019-09-17 21:38:16 +00:00
lda $44
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L1127: nop
Fix code tracing bug If you set things up just right, it's possible for flag status changes to fail to get merged. Added a regression test to 1003-flags-and-branches. Also, tweaked the instruction operand editor to be a bit smoother from the keyboard: added alt-key shortcuts, and put the focus on the OK button after creating/editing a label so you can just hit the return key twice.
2019-09-17 21:38:16 +00:00
rep #$20
Initial file commit
2018-09-28 17:05:11 +00:00
.a16
sep #$10
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
jsr @L1143
Initial file commit
2018-09-28 17:05:11 +00:00
rep #$30
.i16
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
jsr @L1149
Initial file commit
2018-09-28 17:05:11 +00:00
sep #$30
.a8
.i8
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
jsr @L1149
Initial file commit
2018-09-28 17:05:11 +00:00
rep #$20
.a16
sep #$10
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
jsr @L1143
Initial file commit
2018-09-28 17:05:11 +00:00
sep #$30
.a8
rts
.a16
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L1143: lda #$1234
Initial file commit
2018-09-28 17:05:11 +00:00
ldx #$ff
rts
.a8
Fix AND/ORA imm flag updater The code was making an unwarranted assumption about how the flags were being set. For example, ORA #$00 can't know if the previous contents of the accumulator were nonzero, only that the instruction hasn't made them nonzero, but instead of marking the Z-flag "indeterminate" it was leaving the flag in its previous state. This produces incorrect results if the previous instruction didn't set its flags from the accumulator contents, e.g. it was an LDX. Test 1003-flags-and-branches has been updated to test these states.
2020-05-02 00:25:18 +00:00
@L1149: lda #$ff
Initial file commit
2018-09-28 17:05:11 +00:00
ldx #$ee
ldy #$dd
rts
Reference in New Issue Copy Permalink