The most important thing with ***embly is establish some conventions with how you use the various pieces of the architecture. Where are your returns going to be stored, what are you going to use different registers for, etc.
It's really not that difficult. Really it's like C with more book keeping involved (like the need to manually ***ign registers to variables or ***ign space on the stack if you have too many variables). I'd just write out your algorithms in pseudocode and then think about where everything goes.
|