On 2015-10-08 14:19, Tom Marchant wrote: (snipped)
If I have a section of code where I want to use an additional
register, I can look at every instruction in that section to see which
registers are used, or I can use the cross-reference.
When adding code to an existing section of assembler, it is also helpful
to know which registers are actually in use and must have their values
retained across this section of code, in addition to which are used in
this section of code. I find comments detailing this at the beginning
of a section of code to be very helpful when trying to maintain the
code. The cross-reference doesn't resolve all register usage problems,
but the improved one sure helps.
An assembler programmer should know the effects of the instructions
that he uses.
Agreed, but it can be very time-consuming to research every instruction
that was already there that (s)he didn't use. With a 1000+
instructions, some will be bound to remain relatively obscure, which how
this subject line came into being, IIRC.
Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone +1.613.523.5500 x216
Email: [email protected]
Visit us online at www.DKL.com
E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
