So I utilize WLA-DX for compilation. It creates a symbol map that looks like this.
230507-11190651.txt
Now, I'm not positive, but I suspect this is just the result of you not having a WLA Symbol parser, and whatever parser you do have is just interpreting the file to the best of its abilities. If this is the case, then it explains why the definitions section(used for variable names) is being output as if they are labels and NOT as variables.
If I'm correct about the lack of a WLA parser, and you plan on implementing a symbol map parser for WLA, here's a link to version 1 and version 2 of their standard.
Thanks, that's right, this format is not supported and the parser is doing its best right now.
The "labels" section of the file is probably working right though.
So I utilize WLA-DX for compilation. It creates a symbol map that looks like this. 230507-11190651.txt Now, I'm not positive, but I suspect this is just the result of you not having a WLA Symbol parser, and whatever parser you do have is just interpreting the file to the best of its abilities. If this is the case, then it explains why the definitions section(used for variable names) is being output as if they are labels and NOT as variables.
If I'm correct about the lack of a WLA parser, and you plan on implementing a symbol map parser for WLA, here's a link to version 1 and version 2 of their standard.