@Janet, your observation is correct and yes, if one were marketing assembler code (or for that matter, code in any language) for integration with LE C/C++, yes, one might well want to ship two versions. One would not "have to" but one might want to in order to sell a complete solution.
You can with a #pragma tell C/C++ "This program is XPLINK in general but call this one routine using non-XPLINK conventions" (and perhaps vice versa) but there is said to be a significant performance penalty, so if your API is intended to be called "a lot" you would need to consider that. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Janet Graff Sent: Monday, August 29, 2016 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." Charles, It doesn't appear that the register conventions for XPLINK and non-XPLINK are compatible. If one were marketing an Assembler API would you have to deliver two versions? One XPLINK and one non-XPLINK? >Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
