Thanks for the correction, Ed. I'm surprised there weren't more errors in it.
Actually, I did present a SHARE session on this twice. Once in 2012 and again in 2018, titled, Saving Your Caller's Registers - Not Your Father's Save Area. -- Tom Marchant On Wed, 26 Jan 2022 07:37:36 -0800, Ed Jaffe <edja...@phoenixsoftware.com> wrote: >Tom, > >You've provided an excellent tutorial describing *exactly* what's >documented in the books about how this is all supposed to work. > >I did find one typo. After "D" returns and "E" gets invoked by "B", you >have "D" saving registers. That should say "E". We knew what you meant. > >This provides the cornerstone of a GREAT SHARE presentation you oughtta >give wunna these days! > >Thanks, > >Ed Jaffe > >On 1/25/2022 6:04 PM, Tom Marchant wrote: >> Shmuel, >> I'm not clear which text and sample code you are looking at. I'm also not >> clear what you mean by B and C. I assume you are looking at the Assembler >> Services Guide, Chapter 2. And I will guess that you are asking about B and >> C in the situation where A calls B, which calls C. I will describe the >> situation where F5SA is used. >[snip] >> Now, suppose D returns and B calls E, which doesn't touch any high halves, >> so it uses the standard save area format. D saves the registers in B's save >> area and ... > > > >-------------------------------------------------------------------------------- >This e-mail message, including any attachments, appended messages and the >information contained therein, is for the sole use of the intended >recipient(s). If you are not an intended recipient or have otherwise >received this email message in error, any use, dissemination, distribution, >review, storage or copying of this e-mail message and the information >contained therein is strictly prohibited. If you are not an intended >recipient, please contact the sender by reply e-mail and destroy all copies >of this email message and do not otherwise utilize or retain this email >message or any or all of the information contained therein. Although this >email message and any attachments or appended messages are believed to be >free of any virus or other defect that might affect any computer system into >which it is received and opened, it is the responsibility of the recipient >to ensure that it is virus free and no responsibility is accepted by the >sender for any loss or damage arising in any way from its opening or use.
