Tom Marchant wrote:
On Tue, 29 Aug 2017 15:59:53 -0400, Thomas David Rivers wrote:
The doc seems ambiguous to me; which leads me down this path
of doing funky save-area machinations to ensure that all registers
are saved - not just the "normal" ones.
STM 14,12,12(13)
hardly constitutes "doing funky save-area machinations".
Saving your caller's registers is a good practice, if for no other reason than
to aid in debugging.
Diagnosing "clever" code that avoids the calling conventions is a PITA.
Oh yes! I *totally* agree - the problem is a little involved... I'm
branching to
some code that wants a save area, but I'm not in position to allocate one.
So - I can't save the incoming registers in the OS-provided area just to
have
the branched-to routine overwrite that... the restore would then not restore
the proper registers.
It's a twisty maze of save-area stuff to be sure...
(It's a "thunk" between two stacks... - these things happen...)
If I didn't have to save/restore R15 and R1, then I could totally get away
with something very close to standard linkage... that's my basic
question/hope.
- Dave Rivers -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
