6502/6502bench
1
0
Fork 0
mirror of https://github.com/fadden/6502bench.git synced 2024-07-06 16:29:03 +00:00
Code Issues Projects Releases Wiki Activity
fa500a2a49
6502bench/SourceGen/SGTestData/20000-numeric-types.dis65

249 lines
3.6 KiB
Plaintext
Raw Normal View History

Initial file commit
2018-09-28 17:05:11 +00:00
### 6502bench SourceGen dis65 v1.0 ###
{
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
"_ContentVersion":3,
"FileDataLength":1200,
"FileDataCrc32":1114187983,
"ProjectProps":{
"CpuName":"6502",
"IncludeUndocumentedInstr":false,
"TwoByteBrk":false,
"EntryFlags":32702671,
"AutoLabelStyle":"Simple",
"AnalysisParams":{
"AnalyzeUncategorizedData":true,
"DefaultTextScanMode":"LowHighAscii",
"MinCharsForString":4,
"SeekNearbyTargets":true,
"SmartPlpHandling":true},
"PlatformSymbolFileIdentifiers":[],
Regression test rework, part 1 The regression tests were written with the assumption that all cross assemblers would support 6502, 65C02, and 65816 code. There are a few that support 65816 partially (e.g. ACME) or not at all. To best support these, we need to split some of the tests into pieces, so that important 6502 tests aren't skipped simply because parts of the test also exercise 65816 code. The first step is to change the regression test naming scheme. The old system used 1xxx for tests without project files, and 2xxx for tests with project files. The new system uses 1xxxN / 2xxxN, where N indicates the CPU type: 0 for 6502, 1 for 65C02, and 2 for 65816. For the 1xxxN tests the new value determines which CPU is used, which allows us to move the "allops" 6502/65C02 tests into the no-project category. For 2xxxN it just allows the 6502 and 65816 versions to have the same base name and number. This change updates the first batch of tests. It involves minor changes to the test harness and a whole bunch of renaming.
2020-06-06 21:22:53 +00:00
"ExtensionScriptFileIdentifiers":["PROJ:20000-numeric-types.cs"],
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
"ProjectSyms":{
Initial file commit
2018-09-28 17:05:11 +00:00
}},
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
Initial file commit
2018-09-28 17:05:11 +00:00
"AddressMap":[{
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
"Offset":0,
"Addr":4096},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
{
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
"Offset":1032,
"Addr":5128},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
{
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
"Offset":1048,
"Addr":5160}],
"TypeHints":[{
"Low":0,
"High":0,
"Hint":"Code"}],
"StatusFlagOverrides":{
Initial file commit
2018-09-28 17:05:11 +00:00
},
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
Initial file commit
2018-09-28 17:05:11 +00:00
"Comments":{
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
"588":"comment on bulk",
"882":"incorrect alignment",
"1032":"note no-op .ORG",
"1048":"meaningful .ORG",
"1128":"end-of-line comment"},
Initial file commit
2018-09-28 17:05:11 +00:00
"LongComments":{
"-2147483647":{
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
"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},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1112":{
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
"Text":"long comment\r\n",
"BoxMode":false,
"MaxWidth":80,
"BackgroundColor":0}},
Initial file commit
2018-09-28 17:05:11 +00:00
"Notes":{
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1144":{
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
"Text":":ETON",
"BoxMode":false,
"MaxWidth":80,
"BackgroundColor":0}},
Initial file commit
2018-09-28 17:05:11 +00:00
"UserLabels":{
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"588":{
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
"Label":"LABEL",
"Value":4684,
"Source":"User",
"Type":"GlobalAddr",
"LabelAnno":"None"},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1064":{
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
"Label":"UserLabel",
"Value":5176,
"Source":"User",
"Type":"GlobalAddr",
"LabelAnno":"None"}},
Initial file commit
2018-09-28 17:05:11 +00:00
"OperandFormats":{
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"23":{
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
"Length":1,
"Format":"NumericLE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"24":{
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
"Length":2,
"Format":"NumericLE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"26":{
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
"Length":3,
"Format":"NumericLE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"29":{
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
"Length":4,
"Format":"NumericLE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"33":{
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
"Length":1,
"Format":"NumericBE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"34":{
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
"Length":2,
"Format":"NumericBE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"36":{
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
"Length":3,
"Format":"NumericBE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"39":{
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
"Length":4,
"Format":"NumericBE",
"SubFormat":"Hex",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"43":{
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
"Length":2,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"46":{
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
"Length":3,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"50":{
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
"Length":4,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"55":{
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
"Length":5,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"61":{
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
"Length":256,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"318":{
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
"Length":257,
"Format":"Fill",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"575":{
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
"Length":1,
"Format":"Dense",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"577":{
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
"Length":10,
"Format":"Dense",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"588":{
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
"Length":64,
"Format":"Dense",
"SubFormat":"None",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"653":{
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
"Length":115,
"Format":"Junk",
"SubFormat":"Align256",
"SymbolRef":null},
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
"769":{
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
"Length":63,
"Format":"Junk",
"SubFormat":"Align64",
"SymbolRef":null},
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
"833":{
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
"Length":31,
"Format":"Junk",
"SubFormat":"Align32",
"SymbolRef":null},
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
"864":{
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
"Length":8,
"Format":"Junk",
"SubFormat":"None",
"SymbolRef":null},
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
"873":{
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
"Length":8,
"Format":"Junk",
"SubFormat":"None",
"SymbolRef":null},
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
"882":{
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
"Length":2,
"Format":"Junk",
"SubFormat":"Align128",
"SymbolRef":null},
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
"884":{
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
"Length":140,
"Format":"Junk",
"SubFormat":"Align256",
"SymbolRef":null},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1192":{
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
"Length":1,
"Format":"NumericLE",
"SubFormat":"Binary",
"SymbolRef":null}},
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
"LvTables":{
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1096":{
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
"Variables":[],
"ClearPrevious":true}},
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"Visualizations":[{
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
"Tag":"vis000488",
"VisGenIdent":"dummy",
"VisGenParams":{
}}],
"VisualizationAnimations":[],
"VisualizationSets":{
Add regression test for data analysis bug The uncategorized data scanner isn't supposed to create strings or ".fill" directives that straddle labels, long comments, notes, visualizations, or ORG directives. The test for crossing an ORG directive is incomplete, and doesn't correctly handle no-op ORGs (where the new address is the same as the old address). The code generator doesn't output ORGs that are hidden inside other things, so we're not generating bad code, but it looks funny on screen and may cause problems later on. The 2004-numeric-types test has the basic .align/.fill/.bulk directive tests, and now has an extended set of tests for uncategorized data region splitting.
2019-12-30 22:09:18 +00:00
"1160":{
"Tags":["vis000488"]}}}
Reference in New Issue Copy Permalink