If someone is curious why:
-- low halves 2-13 are expected to be preserved, but
-- high halves 2-14 are expected to preserved
it relates to a call sequence that involves an old module that has no idea
that high halves even exist, one case where that old module is entered via
BASSM and returns vi
On 6/13/2016 3:26 PM, Charles Mills wrote:
Makes sense. It does seem to me that I have seen code -- kids, don't try this
at home -- that used R14 as a temporary base register on return from a call.
You know, back in the pre-branch-relative days when you could be desperate for
a base register.
PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LINK and high order word of R1
Makes sense. It does seem to me that I have seen code -- kids, don't try this
at home -- that used R14 as a temporary base register on return from a call.
You know, back in the pre-branch-relative days when you cou
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Marchant
Sent: Monday, June 13, 2016 2:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LINK and high order word of R1
On Mon, 13 Jun 2016 16:14:25 -0500, Tom Marchant wrote:
>It seems to me that the low ha
On Mon, 13 Jun 2016 16:14:25 -0500, Tom Marchant wrote:
>It seems to me that the low half of 14 should be unchanged as well, but that's
>not what the book says.
Looking over my correspondence with Peter when he was rewriting Chapter 2, I
asked about the low half of R14. He replied, quite correc
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Marchant
Sent: Monday, June 13, 2016 2:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LINK and high order word of R1
On Mon, 13 Jun 2016 14:05:40 -0700, Charles Mills wrote:
>Okay, got it. The rules for a called program and
On Mon, 13 Jun 2016 14:05:40 -0700, Charles Mills wrote:
>Okay, got it. The rules for a called program and the rules for the IBM macros
>are the same (except as otherwise explicitly specified):
>
>- The high halves of R2 through R13 must go back as they arrived.
>- The high halves of R14 through
order word of R1
On Mon, 13 Jun 2016 11:19:06 -0700, Charles Mills wrote:
>In the description of LINK in Assembler Services I read
>
>...
>
>Does that mean that for standard "old-fashioned" AMODE 31 72-byte savearea
>linkage I am obligated to save the high word of R1 befo
On Mon, 13 Jun 2016 11:19:06 -0700, Charles Mills wrote:
>In the description of LINK in Assembler Services I read
>
>...
>
>Does that mean that for standard "old-fashioned" AMODE 31 72-byte savearea
>linkage I am obligated to save the high word of R1 before issuing LINK in a
>called program? If so
ee.
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Monday, June 13, 2016 3:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LINK and high order word of R1
So you are saying "if you write a standard (legacy
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Monday, June 13, 2016 12:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LINK and high order word of R1
On Mon, 13 Jun 2016 11:19:06 -0700, Charles Mills wrote:
>
>
ubject: Re: LINK and high order word of R1
On 6/13/2016 11:18 AM, Charles Mills wrote:
> Does that mean that for standard "old-fashioned" AMODE 31 72-byte
> savearea linkage I am obligated to save the high word of R1 before
> issuing LINK in a called program? If so, this would
On Mon, 13 Jun 2016 11:19:06 -0700, Charles Mills wrote:
>
>Does that mean that for standard "old-fashioned" AMODE 31 72-byte savearea
>linkage I am obligated to save the high word of R1 before issuing LINK in a
>called program? If so, this would seem to be a compatibility issue for older
>code tha
On 6/13/2016 11:18 AM, Charles Mills wrote:
Does that mean that for standard "old-fashioned" AMODE 31 72-byte savearea
linkage I am obligated to save the high word of R1 before issuing LINK in a
called program? If so, this would seem to be a compatibility issue for older
code that uses LINK. Or i
In the description of LINK in Assembler Services I read
If the LINK is not successful and the caller provided an ERRET exit to
receive
control, the GPRs contain the following:
Register Contents
...
1
Bits 0-31 of the 64 bit register contain the abend reason code for the abend
code for the ABEND th
15 matches
Mail list logo
