Re: BASR to AMODE 64 (Baseless code)

2019-12-03 Thread Seymour J Metz
Subject: Re: BASR to AMODE 64 (Baseless code) On Monday, December 2, 2019, 02:56:13 PM PST, Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > In the source? Branch around them or use LOCTR? What difference > does it make as long as instructions plus data d

Re: BASR to AMODE 64 (Baseless code)

2019-12-03 Thread Seymour J Metz
From: IBM Mainframe Assembler List on behalf of Ngan, Robert Sent: Tuesday, December 3, 2019 4:27 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: BASR to AMODE 64 (Baseless code) We use TWO LOCTR's, one for constants required to be within 4K of the base register and a second

Re: BASR to AMODE 64 (Baseless code)

2019-12-03 Thread Ngan, Robert
: Re: BASR to AMODE 64 (Baseless code) On Monday, December 2, 2019, 02:56:13 PM PST, Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > In the source? Branch around them or use LOCTR? What difference > does it make as long as instructions plus

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Charles Mills
-LIST@LISTSERV.UGA.EDU Subject: Re: BASR to AMODE 64 (Baseless code) Even when using "baseless" code, I like to keep ONE register as the base/entry point of the module (plus what ever is needed for constant/data areas beyond the first 4K). Having a register thus set makes looking at a d

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Charles Mills
[mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, December 2, 2019 2:56 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: BASR to AMODE 64 (Baseless code) On 2019-12-02, at 13:02:39, Tom Marchant wrote: > > On Mon, 2 Dec 2019 19:27:42 +, Keith Moe wrote: >

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Paul Gilmartin
On 2019-12-02, at 13:02:39, Tom Marchant wrote: > > On Mon, 2 Dec 2019 19:27:42 +, Keith Moe wrote: > >> Even when using "baseless" code, I like to keep ONE register >> as the base/entry point of the module (plus what ever is >> needed for constant/data areas beyond the first 4K). > >

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Ed Jaffe
On 12/2/2019 12:02 PM, Tom Marchant wrote: Locating your constants at the beginning of the program allows you to do that without sacrificing a register. Prezactly! That's what we do (using LOCTRs)... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Ed Jaffe
On 12/2/2019 12:02 PM, Tom Marchant wrote: Locating your constants at the beginning of the program allows you to do that without sacrificing a register. Prezactly! That's what we do (using LOCTRs)... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Tom Marchant
On Mon, 2 Dec 2019 19:27:42 +, Keith Moe wrote: >Even when using "baseless" code, I like to keep ONE register >as the base/entry point of the module (plus what ever is >needed for constant/data areas beyond the first 4K). Locating your constants at the beginning of the program allows you

Re: BASR to AMODE 64 (Baseless code)

2019-12-02 Thread Keith Moe
Even when using "baseless" code, I like to keep ONE register as the base/entry point of the module (plus what ever is needed for constant/data areas beyond the first 4K). Having a register thus set makes looking at a dump easier as this base register (90% of the time R12) points to the current