> how hard is it to save your registers in your own R13 area, write an inline 
> WTO

VERY hard if you are on an SRB, X-memory, or hold any locks.

> IMHO an ABEND macro with a unique abend code is far preferable to any of the 
> discussed techniques except during actual development unit testing

Agreed.

Charles


-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On 
Behalf Of Farley, Peter x23353
Sent: Thursday, May 11, 2017 11:23 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Performance of Decimal Floating Point Instruction

PMFJI, but really, even for non-LE subroutines how hard is it to save your 
registers in your own R13 area, write an inline WTO with message indicating 
where and why you want to blow up and an ABEND macro right after?  Yes, the WTO 
is non-reentrant.  Making it reentrant is not that hard.  IMHO an ABEND macro 
with a unique abend code is far preferable to any of the discussed techniques 
except during actual development unit testing (before any client/user ever sees 
it), but maybe that's just me.

Peter

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On 
Behalf Of John McKown
Sent: Thursday, May 11, 2017 1:52 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Performance of Decimal Floating Point Instruction

On Thu, May 11, 2017 at 12:32 PM, Charles Mills <charl...@mcn.org> wrote:

> And one of these days the architecture starts allowing EX of an EX and 
> it fails the bite test.
>

​<EX discussion and old hardware description snipped>


> Charles
>

-- 


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

Reply via email to