: Getting the Last Condition Code
From: "Charles Mills"
Sent: Tuesday, December 11, 2018 8:33 AM
> It is a way of forcing a condition code of "high." (Too lazy to look up the
> bit value.)
Crummy coding.
> Similarly *,255 would force "low" and CR 0,0 would force "equal/zero."
ditto.
From: "Charles Mills"
Sent: Tuesday, December 11, 2018 8:33 AM
It is a way of forcing a condition code of "high." (Too lazy to look up the bit
value.)
Crummy coding.
Similarly *,255 would force "low" and CR 0,0 would force "equal/zero."
ditto.
---
This email has been checked for
And that is why this technique is so bad. I'm somewhat sympathetic to a
small routine that naturally would return the CC, say, a compare routine.
But "faking" the CC instead of using a return code saves nothing; and costs
clarity, besides the problem that kicked off this thread.
sas
On Mon, Dec
ERV.UGA.EDU] On
Behalf Of Tom Marchant
Sent: Monday, December 10, 2018 1:14 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition Code
On Sat, 8 Dec 2018 02:34:20 +, Alan Atkinson wrote:
>CLI *,0 and *,255
Perhaps I'm being dense, but what do you mean?
Surely not
On Sat, 8 Dec 2018 02:34:20 +, Alan Atkinson wrote:
>CLI *,0 and *,255
Perhaps I'm being dense, but what do you mean?
Surely not "compare the byte at the current location counter" which for CLI
will always be X'95'.
--
Tom Marchant
Speaking as someone who has worked on OS and I/O subsystem
development for more than 45 years, I wholeheartedly agree with the
comments and observations posted by Brent Longborough. I've always
found the style of invoking some function and depending upon the
Condition Code upon return to be
, 2018 07:48
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Reply to: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition Code
The RC in our case is the CC. Type in haste repent at leisure.
Equal - ok, low - bad, high - unexpected.
We don’t (say) set an 8 in r15 everywhere.
Allows us
The RC in our case is the CC. Type in haste repent at leisure.
Equal - ok, low - bad, high - unexpected.
We don’t (say) set an 8 in r15 everywhere.
Allows us to branch conditionally without requiring a compare after the return.
> On Dec 8, 2018, at 3:58 AM, Robin Vowels wrote:
>
>
>
On 2018-12-08 05:00, ASSEMBLER-LIST automatic digest system wrote:
> Date:Sat, 8 Dec 2018 02:34:20 +
> From:Alan Atkinson
> Subject: Re: Getting the Last Condition Code
>
> So smelly or not we have a lot of stuff that branches conditionally based on
> return c
From: "Alan Atkinson"
Sent: Saturday, December 08, 2018 1:34 PM
So smelly or not we have a lot of stuff that branches conditionally based on
return codes
Nothing unusual about that.
Has nothing to do with condition codes.
from whatever was just called. CLI *,0 and *,255 along with CR
So smelly or not we have a lot of stuff that branches conditionally based on
return codes from whatever was just called. CLI *,0 and *,255 along with CR
R11,R11 gives a range of options for indicating if something was good, bad or
indifferent.
The ability to insert (say) a logging routine to
From: "esst...@juno.com"
Sent: Saturday, December 08, 2018 12:49 AM
Binyamin Thank YouThose are the two instructions I could not remember
There's a good programming manual available.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
From: "Brent Longborough"
Sent: Friday, December 07, 2018 11:24 PM
IMHO this is a Code Smell.
If you need the CC in order to print it out for debugging, it's probably
more useful to print the data that led to that CC.
If you want to save the CC, go off somewhere and do something else, and
That's the one Thanks Alan
-- Original Message --
From: Alan Atkinson
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition code
Date: Fri, 7 Dec 2018 01:39:54 +
IPM?
ALAN ATKINSON | SR. DIRECTOR SOFTWARE ARCHITECTURE
T 212 633 5313 |
aatkin
Binyamin Thank YouThose are the two instructions I could not remember
-- Original Message --
From: Binyamin Dissen
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition code
Date: Fri, 7 Dec 2018 01:11:25 +0200
IPM
Can be restored by
SPM
On Thu, 6 Dec
IMHO this is a Code Smell.
If you need the CC in order to print it out for debugging, it's probably
more useful to print the data that led to that CC.
If you want to save the CC, go off somewhere and do something else, and
restore the CC when you get back, that can be buggy and make debugging
BALR only inserts the cc in 24-bit mode.
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Robin Vowels
Sent: 07 December 2018 01:08
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition code
BALR
On 7/12
There's also EPSW, which gives you a lot more than just the condition code
and program mask.
- mb
IBM Mainframe Assembler List wrote on
12/06/2018 10:03:39 PM:
> BALR should also lead the OP to other similar instructions to do what
> he wants.
BALR should also lead the OP to other similar instructions to do what
he wants.
- Original Message -
From: "IBM Mainframe Assembler List" @listserv.uga.edu>
To:
Cc:
Sent:Thu, 6 Dec 2018 17:50:26 -0700
On 2018-12-06, at 16:07:36, Robin Vowels wrote:
> BALR
>
What AMODE?
:02 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Getting the Last Condition code
EXTERNAL
==
Branch (or Jump) on condition :)
> -Original Message-
> From: IBM Mainframe Assembler List [mailto:AS
On 2018-12-06, at 16:07:36, Robin Vowels wrote:
> BALR
>
What AMODE?
> On 7/12/2018 9:14 AM, esst...@juno.com wrote:
>> Hi,I seeem to recall am instruction that returned the last/current condition
>> code. Does any one Know the name of this instruction or its OP code ?
-- gil
BALR
On 7/12/2018 9:14 AM, esst...@juno.com wrote:
Hi,I seeem to recall am instruction that returned the last/current condition
code. Does any one Know the name of this instruction or its OP code ?
.
.
Paul D'Angelo
.
.
> Hi,I seeem to recall am instruction that returned the last/current
condition code. Does any one Know the name of this > instruction or its OP
code ?
Apart from fishing it out of bits 18-19 in the PSW after the EPSW
instruction?
Adam Johanson
Email: adam.johan...@us.ibm.com
Branch (or Jump) on condition :)
> -Original Message-
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
> l...@listserv.uga.edu] On Behalf Of esst...@juno.com
> Sent: Thursday, December 06, 2018 2:15 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: Getting the Last Condition code
In what environment?
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of esst...@juno.com
Sent: Thursday, December 06, 2018 5:15 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Getting the Last Condition code
Hi,I seeem to recall
25 matches
Mail list logo
