Gerhard Adam wrote:
One GREAT example is the IBM macros' use of branch rather than jump
instructions. Yes, they work as documented, but they conflict with the
exploitation of the (wonderful!) new base-register-constraint-relief
jump
instructions.
Check macro IEABRC.
IEABRC converts based branches to relative branches. Thus, it affects
only *some* of the IBM macros with addressability issues rendering it a
partial solution at best. In addition, IEABRC converts *all* of the
program's based branches from the COPY point forward -- making it
suitable only for simple/small programs. IEABRC _causes_ assembly errors
in more complex programs!
What is desperately needed is a way to PUSH/POP the effects of IEABRC
around just the individual macro invocations for which it has a positive
impact. I provide one example of how to do this in Tampa SHARE Session
8160
http://shareew.prod.web.sba.com/client_files/callpapers/attach/SHARE_in_Tampa_Bay/S8160EJ104351.pdf.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
