6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-07-13 14:29:23 +00:00
Code Issues Projects Releases Wiki Activity
676ab2554d
6502bench/SourceGen/SGTestData/2004-numeric-types.dis65

73 lines
2.8 KiB
Plaintext
Raw Normal View History

Initial file commit
2018-09-28 17:05:11 +00:00
### 6502bench SourceGen dis65 v1.0 ###
{
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump.
2019-10-19 03:28:02 +00:00
"_ContentVersion":2,"FileDataLength":1024,"FileDataCrc32":-1387500320,"ProjectProps":{
"CpuName":"6502","IncludeUndocumentedInstr":false,"TwoByteBrk":false,"EntryFlags":13566159,"AutoLabelStyle":"Simple","AnalysisParams":{
"AnalyzeUncategorizedData":true,"DefaultTextScanMode":"LowHighAscii","MinCharsForString":4,"SeekNearbyTargets":false,"SmartPlpHandling":true},
Initial file commit
2018-09-28 17:05:11 +00:00
"PlatformSymbolFileIdentifiers":[],"ExtensionScriptFileIdentifiers":[],"ProjectSyms":{
}},
"AddressMap":[{
"Offset":0,"Addr":4096}],"TypeHints":[{
"Low":0,"High":0,"Hint":"Code"}],"StatusFlagOverrides":{
},
"Comments":{
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump.
2019-10-19 03:28:02 +00:00
"566":"comment","882":"incorrect alignment"},
Initial file commit
2018-09-28 17:05:11 +00:00
"LongComments":{
"-2147483647":{
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump.
2019-10-19 03:28:02 +00:00
"Text":"Project file was edited to get all big-endian data types, and to have an incorrect .junk alignment directive.","BoxMode":false,"MaxWidth":80,"BackgroundColor":0}},
Initial file commit
2018-09-28 17:05:11 +00:00
"Notes":{
},
"UserLabels":{
"566":{
"Label":"LABEL","Value":4662,"Source":"User","Type":"LocalOrGlobalAddr"}},
"OperandFormats":{
"1":{
"Length":1,"Format":"NumericLE","SubFormat":"Hex","SymbolRef":null},
"2":{
"Length":2,"Format":"NumericLE","SubFormat":"Hex","SymbolRef":null},
"4":{
"Length":3,"Format":"NumericLE","SubFormat":"Hex","SymbolRef":null},
"7":{
"Length":4,"Format":"NumericLE","SubFormat":"Hex","SymbolRef":null},
"11":{
"Length":1,"Format":"NumericBE","SubFormat":"Hex","SymbolRef":null},
"12":{
"Length":2,"Format":"NumericBE","SubFormat":"Hex","SymbolRef":null},
"14":{
"Length":3,"Format":"NumericBE","SubFormat":"Hex","SymbolRef":null},
"17":{
"Length":4,"Format":"NumericBE","SubFormat":"Hex","SymbolRef":null},
"21":{
"Length":2,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"24":{
"Length":3,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"28":{
"Length":4,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"33":{
"Length":5,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"39":{
"Length":256,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"296":{
"Length":257,"Format":"Fill","SubFormat":"None","SymbolRef":null},
"553":{
"Length":1,"Format":"Dense","SubFormat":"None","SymbolRef":null},
"555":{
"Length":10,"Format":"Dense","SubFormat":"None","SymbolRef":null},
"566":{
Add junk/align directives Sometimes there's a bunch of junk in the binary that isn't used for anything. Often it's there to make things line up at the start of a page boundary. This adds a ".junk" directive that tells the disassembler that it can safely disregard the contents of a region. If the region ends on a power-of-two boundary, an alignment value can be specified. The assembly source generators will output an alignment directive when possible, a .fill directive when appropriate, and a .dense directive when all else fails. Because we're required to regenerate the original data file, it's not always possible to avoid generating a hex dump.
2019-10-19 03:28:02 +00:00
"Length":64,"Format":"Dense","SubFormat":"None","SymbolRef":null},
"631":{
"Length":137,"Format":"Junk","SubFormat":"Align256","SymbolRef":null},
"769":{
"Length":63,"Format":"Junk","SubFormat":"Align64","SymbolRef":null},
"833":{
"Length":31,"Format":"Junk","SubFormat":"Align32","SymbolRef":null},
"864":{
"Length":8,"Format":"Junk","SubFormat":"None","SymbolRef":null},
"873":{
"Length":8,"Format":"Junk","SubFormat":"None","SymbolRef":null},
"882":{
"Length":2,"Format":"Junk","SubFormat":"Align128","SymbolRef":null},
"884":{
"Length":140,"Format":"Junk","SubFormat":"Align256","SymbolRef":null}},
"LvTables":{
}}
Reference in New Issue Copy Permalink