t: 22. oktober 2020 15:58
Til: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Emne: RES: Conditional MVCL macro?
MVC moves up to 256 bytes, not 255
-Mensagem original-
De: IBM Mainframe Assembler List Em nome de
Robin Vowels Enviada em: quinta-feira, 22 de outubro de 2020 05:03
Para: ASSEMBLER
MVC moves up to 256 bytes, not 255
-Mensagem original-
De: IBM Mainframe Assembler List Em nome
de Robin Vowels
Enviada em: quinta-feira, 22 de outubro de 2020 05:03
Para: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Assunto: Re: Conditional MVCL macro?
- Original Message -
From: "
On 2020-10-22, at 02:02:56, Robin Vowels wrote:
>
> You need to test R15 being zero. Subtracting 1 and then doing an EX
> is potentially dangerous.
>
I wonder whether avoiding this hazard was motivation for
CMS MDFS and SFS and early MVS RECFM=V prohibiting empty
records.
-- gil
- Original Message -
From: "Willy Jensen"
Sent: Wednesday, October 21, 2020 12:04 AM
Extract from a larger macro. And no, I was not overly concerned with
performance.
.* r15 : length
.* r14 -> source
On Tue, 20 Oct 2020 16:58:52 -0400 Steve Smith
said:
And for something completely different... sometimes I use MVCK for
a variable-length move instead of EX/MVC or MVCL. I haven't done
any performance tests, because I haven't used it in
performance-critical code (and it does have a wa
.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Ed Jaffe [edja...@phoenixsoftware.com]
Sent: Wednesday, October 21, 2020 1:46 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
On 10/21/2020 10:36 AM
On 10/21/2020 10:36 AM, Seymour J Metz wrote:
Which? Either is subject to an access violation crossing page boundaries. For MVCL, I
don't know of any special significance to 256KiB. For MVCOS, assuming no page fault,
256 < 4096, but I don't know of any significance of 256 rather than, e.g., 128
a.edu]
Sent: Wednesday, October 21, 2020 12:07 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
On 2020-10-21, at 09:20:31, Seymour J Metz wrote:
>
> Unless performance is an issue, I generally opt for simplicity. If
> performance is an issue I encapsulate it i
PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
On 10/21/2020 8:22 AM, Seymour J Metz wrote:
> 4K is indeed an architected limit for MVCOS, but for MVCLE it's
> "CPU-determined number of bytes".
But nicely it will always complete the move if it is <=25
On 10/21/2020 8:22 AM, Seymour J Metz wrote:
4K is indeed an architected limit for MVCOS, but for MVCLE it's "CPU-determined
number of bytes".
But nicely it will always complete the move if it is <=256 bytes. So you
don't need the loop for short moves.
--
Phoenix Software International
Edw
On 2020-10-21, at 09:20:31, Seymour J Metz wrote:
>
> Unless performance is an issue, I generally opt for simplicity. If
> performance is an issue I encapsulate it in a macro that generates different
> code for different processors.
>
It's harder for an EQUated symbolic length; worse yet for
a
Pieter Wiid [pw...@mweb.co.za]
Sent: Wednesday, October 21, 2020 2:22 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
MVCOS? Also needs to be re-driven after 4K
Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Dan Greiner [dan_grei...@att.net]
Sent: Tuesday, October 20, 2020 11:42 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
One of the questions that I always ask in response to concerns about whether
one
MVCOS? Also needs to be re-driven after 4K
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Steve Smith
Sent: 20 October 2020 22:59
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
There's actually
.com
>
>
>-Original Message-
>From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
>Behalf Of Mike Hochee
>Sent: Tuesday, October 20, 2020 12:40 PM
>To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
>Subject: Re: Conditional MVCL macro?
>
>T
One of the questions that I always ask in response to concerns about whether
one instruction is better than another is, "Do you ever expect to recoup the
number of instructions needed to reassemble, rebind, and retest the code?"
Assuming that the answer is "Yes, this code is executed a gazillio
@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Unless I am thinking fuzzily, an interrupted MVCL leaves the PSW pointing to
the MVCL (not past it) and the relevant registers incremented and
decremented appropriately, so the supervisor may dispatch other tasks on the
affected CPU, let them run as
_
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Steve Smith [sasd...@gmail.com]
Sent: Tuesday, October 20, 2020 6:36 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Interrupts can only be handled between instructions (don
So it was written, and it is so done.
sas
On Tue, Oct 20, 2020 at 6:35 PM Charles Mills wrote:
> Unless I am thinking fuzzily, an interrupted MVCL leaves the PSW pointing
> to
> the MVCL (not past it) and the relevant registers incremented and
> decremented appropriately, so the supervisor may d
Interrupts can only be handled between instructions (don't ask me how
pipelining figures) except, MVCL has the potential to delay that too
long, so it (and a handful of others) were made to be interruptible.
Probably, that just means the micro/milli-code program gets interrupted
between micro/
@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
On 2020-10-20, at 14:58:52, Steve Smith wrote:
>
> There's actually a big difference between MVCL being interruptible, and
> MVCLE stopping periodically before it's finished. The latter is not
> interruptible, it just s
I’d say you were both correct.
Keven
On Tue, Oct 20, 2020 at 5:01 PM -0500, "Paul Gilmartin"
<0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
On 2020-10-20, at 14:58:52, Steve Smith wrote:
>
> There's actually a big d
On 2020-10-20, at 14:58:52, Steve Smith wrote:
>
> There's actually a big difference between MVCL being interruptible, and
> MVCLE stopping periodically before it's finished. The latter is not
> interruptible, it just stops before completion periodically for the program
> to do something else if
Architect
Precisely.com
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Mike Hochee
Sent: Tuesday, October 20, 2020 4:40 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
This message originated Exter
be
> the explanation. I'm not a hardware guy, so just guessing.
>
> Chris Blaicher
> Technical Architect
> Precisely.com
>
>
> -Original Message-
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
> On Behalf Of Christopher Y. Blaicher
. Blaicher
Sent: Tuesday, October 20, 2020 3:09 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Caution! This message was sent from outside your organization.
There may be a hint to the reason for the jump in the explanation of MVCLE,
programming note 3.
"The
ERV.UGA.EDU] On
Behalf Of Christopher Y. Blaicher
Sent: Tuesday, October 20, 2020 2:47 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
This message originated Externally. Use proper judgement and caution with
attachments, links, or responses.
I just re-ran a test on
e
boundaries.
Chris Blaicher
Technical Architect
Precisely.com
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Charles Mills
Sent: Tuesday, October 20, 2020 1:57 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditio
2020 10:52 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
MVCL is, and always has been, interruptible.
COBOL version was 6.3 using ARCH(13) OPT(2)
-Original Message-
From: IBM Mainframe Assembler List On
Behalf Of John Melcher
Sent: Tuesday, October 20, 2020 12:09
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
JES2 has had a $MVCL macro since SP2.2.0.
What
:09 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
JES2 has had a $MVCL macro since SP2.2.0.
What version of COBOL, I wonder?
The COBOL compiler for a 4000 byte move, from to the same with OPT(2)
generates
LAY R10,5072(,R9) FROM
LA R7,1072(
:54 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
@Ed, can you elaborate a little on your reasoning? (Not doubting it; just
curious.) Is it that the interruptibility provides a significant improvement
over MVCL? Or the support for lengths greater than 16M? Or ... ?
When
, 2020 12:40 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
This message originated Externally. Use proper judgement and caution with
attachments, links, or responses.
Really interesting thread to start the day with!
Our experience has been that the MVC loops are
Sent: Tuesday, October 20, 2020 12:12 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Caution! This message was sent from outside your organization.
The COBOL compiler for a 4000 byte move, from to the same with OPT(2) generates
LAY R10,5072(,R9) FROM
LA R7,
On 10/20/2020 8:54 AM, Charles Mills wrote:
@Ed, can you elaborate a little on your reasoning? (Not doubting it; just
curious.) Is it that the interruptibility provides a significant improvement
over MVCL? Or the support for lengths greater than 16M? Or ... ?
MVCL with anything other than zero pa
JES2 has had a $MVCL macro since SP2.2.0.
What version of COBOL, I wonder?
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Charles Mills
Sent: Tuesday, October 20, 2020 12:05 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
*** External
M
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Really interesting thread to start the day with!
Our experience has been that the MVC loops are typically faster, up to a
point, that being about 30-40 instructions in the pipeline and as mentioned,
and this seemed
Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of baron_car...@technologist.com
Sent: Tuesday, October 20, 2020 12:12 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
Caution! This message was sent from outside your
at 4097 bytes.
-Original Message-
From: IBM Mainframe Assembler List On
Behalf Of Charles Mills
Sent: Tuesday, October 20, 2020 10:54
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
@Ed, can you elaborate a little on your reasoning? (Not doubting it; just
020 9:06 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
>
> What is the effect of the conditional branch and the EX on the pipeline? Are
> the performance tradeoffs the same on all supported processors? Also, tuning
> code for a current processor may slow
Jaffe
Sent: Tuesday, October 20, 2020 6:52 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Conditional MVCL macro?
We've switched almost exclusively to MVCLE except for short,
fixed-length moves.
We've switched almost exclusively to MVCLE except for short,
fixed-length moves.
On 10/20/2020 5:42 AM, Tony Thigpen wrote:
I have several programs that work with buffers and moving random
length data around using MVCLs. I am considering writing a
'conditional MVCL' macro t
SSEMBLER-LIST@LISTSERV.UGA.EDU
Emne: Conditional MVCL macro?
I have several programs that work with buffers and moving random length data
around using MVCLs. I am considering writing a 'conditional MVCL'
macro that, at runtime, looks at the lengths and either executes the MVCL or
bypasse
>
> What is the effect of the conditional branch and the EX on the pipeline? Are
> the performance tradeoffs the same on all supported processors? Also, tuning
> code for a current processor may slow it down on a new one.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
In
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Tony Thigpen [t...@vse2pdf.com]
Sent: Tuesday, October 20, 2020 8:42 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Conditional MVCL macro?
I have several programs that work with buffers and
I have several programs that work with buffers and moving random length
data around using MVCLs. I am considering writing a 'conditional MVCL'
macro that, at runtime, looks at the lengths and either executes the
MVCL or bypasses it and uses a MVC via EX.
I know this would generat
46 matches
Mail list logo