PB's Own ASM Reference
Posted: Fri Apr 16, 2004 12:08 am
It's great to have the external Help files, including the ones for ASM.
Unfortunately, there is nothing immediately available for methods of
tying PB and ASM together. I think a section on passing and returning
parameters, and defining or calling routines in libraries would be useful.
I noted that you can crash the PB debug mode if you try to use
DEBUG commands anywhere in a ASM process. Since the register
display is limited (only shows the extended register view, and contents
shown only in decimal), that makes it somewhat difficult to tell what is
going on in an ASM process when trying to step through it.
I know that PB isn't responsible for quirks found with FASM, but I had some real problems, until I realized from studying some examples that the line lables can be in any case, but the instruction references to those line labels require a leading "l_" and the label has to be completely in lower case.
That, too, should be covered in the PB/ASM interface information.
I haven't found anything on it, but can't you embed compiler directives
for controlling such things as enabling the inline ASM feature? That would make sure that the inline code compiles without error.
Unfortunately, there is nothing immediately available for methods of
tying PB and ASM together. I think a section on passing and returning
parameters, and defining or calling routines in libraries would be useful.
I noted that you can crash the PB debug mode if you try to use
DEBUG commands anywhere in a ASM process. Since the register
display is limited (only shows the extended register view, and contents
shown only in decimal), that makes it somewhat difficult to tell what is
going on in an ASM process when trying to step through it.
I know that PB isn't responsible for quirks found with FASM, but I had some real problems, until I realized from studying some examples that the line lables can be in any case, but the instruction references to those line labels require a leading "l_" and the label has to be completely in lower case.
That, too, should be covered in the PB/ASM interface information.
I haven't found anything on it, but can't you embed compiler directives
for controlling such things as enabling the inline ASM feature? That would make sure that the inline code compiles without error.