On 11/17/2021 1:36 AM, Jonathan Scott wrote:
We have just shipped the PTFs for APAR PH42050 which allows a
dependent USING instruction to be resolved using a 20-bit signed
displacement provided that the specified OPTABLE is one which
supports instructions with that capability.
|
> In that scenario, offset 4 of Xs save area will no longer contain
> FnSA, and can thus be identified as the forward pointer of a 72-bytesave
area.
The point that several recent posts have been trying to make is that the
contents of word 1 indicate how the registers were saved in the
Yes thank you very much this worked:
SETC 'C''R'''
_MNOTE SETC DOUBLE('')
MNOTE *,'&WHAT = _MNOTE'
generates the MNOTE:
2111+*, = C'R'
In that scenario, offset 4 of Xs save area will no longer contain FnSA, and can
thus be identified as the forward pointer of a 72-byte save area.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List
> The one case where there could be an issue is if the
> routine calls both code expecting a 72-byte save area and code
> calling a 144-byte area.
>
> If the linkage conventions are followed, under what circumstances
> would you be unable to follow the forward chain with a little bit of
work?
My "Assuming that the caller has initialized the save area and subsequently
used it in accordance with IBM linkage conventions" took into account what
Peter wrote. If the caller does not follow the conventions, all bets are off.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Nope! Read what Peter wrote.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Seymour J Metz
Sent: Wednesday, December 1, 2021 10:27 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Base-less macros
Assuming that the
Assuming that the caller has initialized the save area and subsequently used it
in accordance with IBM linkage conventions, offset 4-7 will contain 4 EBCDIC
characters ending iin SA only if it is 144 bytest long; the forward link of a
72-byte save area should never be odd. The one case where
Thanks for the clarification. I seem to be a slow learner.
> It's perfectly fine to use high halves in AMODE 31
People seem to conflate AMODE 64 with the usage of high halves. Writing in
AMODE 64 is kind of a big deal (been there, etc.). Using the high halves for
arithmetic and such is a piece
Charles wrote:
Ah! I have not been clear on the convention. As I read it now, the called
program puts one of the FnSA strings in its *new* save area to indicate
how
*it* previously stored the registers in its entry save area.
This point has been made multiple times in this forum and in
10 matches
Mail list logo
