NASM Forum > Announcements
NASM - Official Recursive Macro Support!
Keith Kanios:
This is an official announcement regarding the rewrite/revamp of the NASM preprocessor, now available as part of the official/main NASM source code starting with NASM 2.10rc2.
This rewrite addresses issues with implementing recursive macros (%rmacro/%irmacro) as previously attempted, %exitmacro and also makes room for new directives.
New NASM Directives:
* %rmacro: Recursive Macro, can be called arbitrarily deep (really high limit [2^20] set to catch infinite loops.)
* %irmacro: Same as above, except case-insensitive like %imacro.
* %exitmacro: Terminates the current macro invocation, much like %exitrep; can be nested in other preprocessor directives (e.g. %if/%endif) within the macro, with exception of another macro, of course.
* %while/%endwhile/%exitwhile: A fusion between %rep and %if.
* %comment/%endcomment: Comment block for long/multi-line comments. A little syntactic sugar, if you will.
* %final: Causes rest of line after %final to be preprocessed after all other "normal" preprocessing is complete. Multiple %final directives work like the x86 stack, LIFO/FILO.
This rewrite also addresses efficiency issues with heavy/nested macro invocations.
Please help us test this rewrite further by downloading/compiling the NASM 2.10rc2 and testing it against your NASM code/snippets.
NASM 2.10rc2 is available for download (source and binaries) at http://www.nasm.us/pub/nasm/releasebuilds/2.10rc2/
Please note that the official documentation will be updated over the next few weeks as we approach an official/stable NASM 2.10 release.
If there are any questions/comments/concerns, please reply to this thread.
Thanks. -Keith
cm:
A bug report. Posting it here as I guess it's on-topic enough (appears to be a 2.10rc2 issue), and the SF.net bug tracker doesn't let me post a new bug for whatever reason.
The Windows executable of 2.10rc2, as distributed, appears to crash on %fatal in included files.
Two files form a simple test case of this; assemble them with the command line "nasm test.asm".
test.asm contains:
--- Code: ---%include "test.mac"
--- End code ---
test.mac contains:
--- Code: ---%fatal Test
--- End code ---
This crashes for me with a GPF.
Notably, a local Windows build compiled by OpenWatcom 1.9 does not crash and outputs the %fatal message as expected. (I tried compiling with Visual Studio 2008 but that didn't work. Probably because of some incompatibility to VS 2005.)
Edit: This simple test case doesn't crash with my OW build, but assembling my whole project crashes the same with either the distributed build or the OW build.
Klod:
Just downloaded Nasm 2.10rc2 win binaries.
Noted decrease in assemble time (faster)
So far all test programs I tried compiled correctly.
One observation:
--- Quote ---%macro mac1 5
%rep %0
%Warning %? %0 %1 %2 %3 %4 %5
%rotate 1
%endrep
%endm
mac1 firstarg,2,3,4,string
--- End quote ---
:7: warning: (mac1:2) %? 5 firstarg 2 3 4 string
Loss of macroname %? %??
Regards
Klod
Cyrill Gorcunov:
--- Quote from: cm on November 08, 2010, 07:28:34 PM ---A bug report. Posting it here as I guess it's on-topic enough (appears to be a 2.10rc2 issue), and the SF.net bug tracker doesn't let me post a new bug for whatever reason.
The Windows executable of 2.10rc2, as distributed, appears to crash on %fatal in included files.
Two files form a simple test case of this; assemble them with the command line "nasm test.asm".
test.asm contains:
--- Code: ---%include "test.mac"
--- End code ---
test.mac contains:
--- Code: ---%fatal Test
--- End code ---
This crashes for me with a GPF.
Notably, a local Windows build compiled by OpenWatcom 1.9 does not crash and outputs the %fatal message as expected. (I tried compiling with Visual Studio 2008 but that didn't work. Probably because of some incompatibility to VS 2005.)
Edit: This simple test case doesn't crash with my OW build, but assembling my whole project crashes the same with either the distributed build or the OW build.
--- End quote ---
The fix pushed upstream as commit 55cc4d04235cb884a885682b5a52f367ec7d50c3.
Please give it a shot by using nasm snapshot. Thanks for report!
Cyrill Gorcunov:
--- Quote from: Klod on November 10, 2010, 03:12:38 AM ---
:7: warning: (mac1:2) %? 5 firstarg 2 3 4 string
Loss of macroname %? %??
Regards
Klod
--- End quote ---
Hi Klod, probably ;) I hope I manage to find time for this issue at this weekend.
Though no promises, not enough spare time :(
But observations from nasm users are quite important for us -- so please continue testing ;)
Navigation
[0] Message Index
[#] Next page
Go to full version