So for implied register references, I use constructs such as the following in my code:
TRT foo,bar
DC 0Y(R1,R2) (IMPLIED REGISTER REFERENCES)
BXLE R3,R4,elsewhere
DC 0Y(R5) (IMPLIED REGISTER REFERENCE)
STFL ignored
DC 0Y(FLCFACL-PSA) (IMPLIED STORAGE REFERENCE)
In addition to revealing implied references of all sorts, it has the advantage of making that revelation right there in the code that you are examining. You don't have to even consider resorting to an xref lookup.
Of course, you have to be methodical about this, but what good is a programmer who is not methodical?
Bye the way, the ancient and orphaned SPF-PC is a great tool for searching entire folders of downloaded assembly listings, it can search all 200+ assembly listings for z/XDC (around 200 mbytes) in a bit less than 30 seconds on the first search. The second search takes around 4 seconds due to Windows disk caching.
One reason I do not include xrefs in my assemblies [besides the fact that I don't need them] is that if I did, then my listings would be around twice as large.
Also, I find that string searches are a FAR[!] faster way of finding stuff than xref lookups.
mtcw,
Dave Cole
At 7/31/2013 06:50 PM, Tom Marchant wrote:
On Wed, 31 Jul 2013 15:17:58 -0700, John Ehrman wrote:
>Paul Gilmartin noted:
>> XREF doesn't reliably list register references.
>
>That's why HLASM provides a register cross-reference (use the RXREF
>option). It not only references explicit register use, symbolic or not,
>but also implicit uses for instructions like LM, M, D, SRDL, and the like.
>For example,
>
> LM R14,R12,12(R13)
>
>shows only three symbol references, but the RXREF shows all sixteen.
Yep. It even shows register 2 being modified by any TRT instruction.
I use it often.
--
Tom Marchant
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: [email protected]
Home page: www.colesoft.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
