6502bench/SourceGen/SGTestData/Expected/2024-ui-edge-cases_cc65.S

         .setcpu "6502"
;         .segment "SEG000"
         .org    $2000
         jmp     L2100

         .byte   "hello, "  ;string should be split by no-op addr change
;         .segment "SEG001"
         .org    $200a
         .byte   "world"
         .byte   $80

;         .segment "SEG002"
         .org    $2100
L2100:   lda     #$00
         sta     addr1-1    ;edit this operand
         sta     addr1
         sta     addr1+1
         jmp     L2121

         .byte   "testing stuff."
addr1:   .byte   "!?---"

L2121:   rts
Correct handling of no-op .ORG statements These were being overlooked because they didn't actually cause anything to happen (a no-op .ORG sets the address to what it would already have been). The assembly source generator works in a way that causes them to be skipped, so everybody was happy. This seemed like the sort of thing that was likely to cause problems down the road, however, so we now split regions correctly when a no-op .ORG is encountered. This affects the uncategorized data analyzer and selection grouping. This changed the behavior of the 2004-numeric-types test, which was visibly weird in the UI but generated correct output. Added the 2024-ui-edge-cases test to provide a place to exercise edge cases when testing the UI by hand. It has some value for the automated regression test, so it's included there. Also, changed the AddressMapEntry objects to be immutable. This is handy when passing lists of them around. 2020-02-28 22:43:03 +00:00			`.setcpu "6502"`
			`; .segment "SEG000"`
			`.org $2000`
			`jmp L2100`

			`.byte "hello, " ;string should be split by no-op addr change`
			`; .segment "SEG001"`
			`.org $200a`
			`.byte "world"`
			`.byte $80`

			`; .segment "SEG002"`
			`.org $2100`
			`L2100: lda #$00`
			`sta addr1-1 ;edit this operand`
			`sta addr1`
			`sta addr1+1`
			`jmp L2121`

			`.byte "testing stuff."`
			`addr1: .byte "!?---"`

			`L2121: rts`