6502bench/SourceGen/SGTestData/Expected/20122-char-encoding_cc65.cfg

# 6502bench SourceGen generated linker script for 20122-char-encoding
MEMORY {
    MAIN: file=%O, start=%S, size=65536;
#    MEM000: file=%O, start=$1000, size=19;
}
SEGMENTS {
    CODE: load=MAIN, type=rw;
#    SEG000: load=MEM000, type=rw;
}
FEATURES {}
SYMBOLS {}
Rework 201XX-char-encoding-X tests We have a single character-encoding test that is cloned 3x so we can exercise the different values for the project's default character set. It was a 65816 test because it tested 16-bit immediate char operands, but that's a very small part of it. The 65816-specific portion is now 20122-char-encoding. The rest is now 201{2,3,4}0-char-encoding-X. 2020-10-19 22:01:02 +00:00			`# 6502bench SourceGen generated linker script for 20122-char-encoding`
Add 2016-char-encoding-a and variations All tests use the same data file and nearly the same project file. The only difference is the default text encoding property setting. For "-a" it's ASCII, for "-p" it's PETSCII, for "-s" it's C64 screen code. Right now this only affects the code generated for 64tass. The test itself is a collection of strings and characters in the supported character encodings. How these are handled varies significantly between assemblers. 2019-08-16 21:53:50 +00:00			`MEMORY {`
			`MAIN: file=%O, start=%S, size=65536;`
Rework 201XX-char-encoding-X tests We have a single character-encoding test that is cloned 3x so we can exercise the different values for the project's default character set. It was a 65816 test because it tested 16-bit immediate char operands, but that's a very small part of it. The 65816-specific portion is now 20122-char-encoding. The rest is now 201{2,3,4}0-char-encoding-X. 2020-10-19 22:01:02 +00:00			`# MEM000: file=%O, start=$1000, size=19;`
Add 2016-char-encoding-a and variations All tests use the same data file and nearly the same project file. The only difference is the default text encoding property setting. For "-a" it's ASCII, for "-p" it's PETSCII, for "-s" it's C64 screen code. Right now this only affects the code generated for 64tass. The test itself is a collection of strings and characters in the supported character encodings. How these are handled varies significantly between assemblers. 2019-08-16 21:53:50 +00:00			`}`
			`SEGMENTS {`
			`CODE: load=MAIN, type=rw;`
			`# SEG000: load=MEM000, type=rw;`
			`}`
			`FEATURES {}`
			`SYMBOLS {}`