In general, but not when there are addressability issues. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Tom Marchant <[email protected]> Sent: Thursday, May 2, 2024 8:49 PM To: [email protected] Subject: Re: IEABRC anomaly Would it help to use IEABRCX and disable it around that macro? -- Tom Marchant On Thu, 2 May 2024 21:50:26 +0000, Seymour J Metz <[email protected]> wrote: >It's not clear that the author ever heard of EX. Some of the code is decades >old, and a mass cleanup is not authorized. I'm not rven sure whether I can get >permission to fix a macro that IEABRC breaks (it uses the BDDD of a B as a >first-time switch. > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 >עַם יִשְׂרָאֵל חַי >נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר > >________________________________________ >From: IBM Mainframe Assembler List <[email protected]> on behalf >of Paul Gilmartin <[email protected]> >Sent: Thursday, May 2, 2024 5:12 PM >To: [email protected] >Subject: Re: IEABRC anomaly > >On 5/2/24 11:16:13, Seymour J Metz wrote: >> Except that IEABRC is only necessary for old code. I've inherited code that >> uses NOP as a switch, overlaying the mask with F. >> . >Self-modifying or EX code!? > >-- >gil
