6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-11-18 15:06:07 +00:00
Code Issues Projects Releases Wiki Activity
635084db9d
6502bench/SourceGen/SGTestData/Expected/20032-labels-and-symbols_acme.S

27 lines
1.8 KiB
ArmAsm
Raw Normal View History

Finish ACME v0.96.4 support There's no easy way to make non-zero-bank 65816 code work, so I'm punting and just generating a whole-file hex dump for those. This renders tests 2007 and 2009 useless, so I'm hesitant to claim that ACME support is fully functional.
2019-08-04 21:48:42 +00:00
;ACME can't handle 65816 code that lives outside bank zero
Fix ACME code gen "overflow" ACME has a "real" PC and a "pseudo" PC. The "real" PC determines the initial position in a 64KB buffer used to hold assembler output. If the amount of code generated runs off the end, the assembler fails with "produced too much code". The source code generator in SourceGen was outputting a "real" PC for the first address range and "psuedo" PCs for any address ranges that followed. This produced nice results for code with a single range, but caused problems for multi-range sources if the initial range was high in memory and a later range was lower in memory. While the assembler isn't actually generating more than 64KB of code, ACME's buffer management was detecting an overflow. Now, if a source file has multiple address ranges, we set the "real" PC to $0000 and use a "pseudo" PC for all ranges. Output for projects with a single address range is unmodified.
2020-05-14 23:37:33 +00:00
* = $0000
!pseudopc $012345 {
Finish ACME v0.96.4 support There's no easy way to make non-zero-bank 65816 code work, so I'm punting and just generating a whole-file hex dump for those. This renders tests 2007 and 2009 useless, so I'm hesitant to claim that ACME support is fully functional.
2019-08-04 21:48:42 +00:00
!hex 18fbe230a9cda9dda90da9eda9fea92da9ffa929a910a9e9a90fa945a923a901
!hex f4edfef44523f40100f45634f41200f4edfef44523f40100f45634f41200a5ce
!hex adce00afce0000adecfeafecfe00adeefeafeefe00ad4623af462301ad4423af
!hex 442301ad5734af573412ad5534af553412c230a9cd00a9dd00a90d01a92910a9
!hex 1000a92900a90000a90000a9edfea9fe00a9ed0ea90e01a90100a94523a92301
!hex a90100a95634a93412a912008050cdedfe452301cd002910100029000000edfe
!hex fe00ed0e0e01452323010100462323010100feedcd0000edfe00fe0000452301
!hex 230100010000cd000000edfe0000fe000000442301002301000001000000a911
!hex 0054011244120154011244120162eeff8200005c001000eaeaeae230ad0030ad
!hex 0031ad0032ad00338039eaeaea62faff62f8ff62f6ff20131020141020151080
!hex e980e880e782e2ff82e0ff82deff4c13104c14104c15105c1310005c1410005c
!hex 151000201610202810202a10202c10202e10203110203410203710203a10203d
!hex 10204010204410204810821801808182838485868788898a8b8c8d8e8f808182
!hex 838485868788898a8b8c8d8e8f808182838485868788898a8b8c8d8e8f808182
!hex 838485868788898a8b8c8d8e8f808182838485868788898a8b8c8d8e8f808182
!hex 838485868788898a8b8c8d8e8f808182838485868788898a8b8c8d8e8f546869
!hex 732069732061206c6f6e6720737472696e672e205075742061206c6162656c20
!hex 616e6420636f6d6d656e74206f6e20697420746f20636f6e6669726d20746861
!hex 7420746865206c6162656c20616e6420636f6d6d656e74206f6e6c7920617070
!hex 656172206f6e20746865206669727374206c696e652e20205468652071756963
!hex 6b2062726f776e20666f78206a756d7073206f76657220746865206c617a7920
!hex 646f67732ea97aa959a934c230a97b56a95a34a9341260
Fix ACME code gen "overflow" ACME has a "real" PC and a "pseudo" PC. The "real" PC determines the initial position in a 64KB buffer used to hold assembler output. If the amount of code generated runs off the end, the assembler fails with "produced too much code". The source code generator in SourceGen was outputting a "real" PC for the first address range and "psuedo" PCs for any address ranges that followed. This produced nice results for code with a single range, but caused problems for multi-range sources if the initial range was high in memory and a later range was lower in memory. While the assembler isn't actually generating more than 64KB of code, ACME's buffer management was detecting an overflow. Now, if a source file has multiple address ranges, we set the "real" PC to $0000 and use a "pseudo" PC for all ranges. Output for projects with a single address range is unmodified.
2020-05-14 23:37:33 +00:00
} ;!pseudopc
Reference in New Issue Copy Permalink