Howdy y'all,
It's an understatement to say that the m4s code has become a bit cluttered. To that end, I've begun to separate the code into modules and scripts. The code code has been moved to MSP430static.pm. msp430static.pl remains as a simple wrapper.
Further, a scripting feature has been added. Scripts reside in $m4s/scripts, and it is my intention to remove all unessential code from MSP430static.pl into the scripting directory. A script is called by name, preceded by a forward slash. The script loadmacros.pl, for example, is called as "/loadmacros". Subdirectories are supported. A matching textfile, loadmacros.txt, contains a short description for generating documentation.
Also, .lib.import.hashed is no longer run by default at initialization. Be sure to call it if you expect to recognize functions.
Please email me if you've any confusion regarding this processor, or have uncovered any bugs therein.
--Travis Goodspeed
<travis at utk.edu>
Sunday, June 29, 2008
Friday, June 27, 2008
r60 with 'graph' directive
I've just committed a minor but useful feature to make my life easier while generating function flow diagrams. The new syntax follows,
echo "select insflow(asm) from code where ...;" | m4s sql graph >foo.dot"
Cheers,
--Travis
echo "select insflow(asm) from code where ...;" | m4s sql graph >foo.dot"
Cheers,
--Travis
Subscribe to:
Posts (Atom)