On 25 June 2018 at 11:49, Binyamin Dissen <[email protected]> wrote: > Since the assembler knows which instructions modify which registers, it would > be nice if there was a way to "protect" a register for a code range. > > Perhaps > > USING area,Rx,protect > > Any alteration of the register until the DROP would cause a warning message on > the instruction. > > Or might such an option exist?
No, but you can do it yourself by post-processing either the Register Xref + Using Map, or the ADATA. Not that I don't think it's a nice option to have. I would prefer to see it generalized so as to allow any register (not just one that is the topic of a USING) be protectable. I've seen code where a loop counter is in a register and the loop is long enough to cover two or more pages, and it's easy to forget in the middle that the loop register can't be used for other things. Typically that register would not be in a USING. Tony H.
