There is lots of room in the E3xx range close to CGH and/or LGH.
E310 to E312 and/or E337 thru E33D
We will see next month.
--
Martin
Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE
more at http://www.picapcpu.de
From: Steve Smith sasd...@gmail.com
Sent: Monday, June 24, 2013 12:24 PM
I've been converting some code to use full 64-bit registers lately, and
was greatly surprised that there appears to be no AGH (Add Halfword (to
64-bit register)). There's LGH, and even CGH, as well as AGHI (much
less
XI** are more important in my opinion.
On Mon, 24 Jun 2013 09:11:12 +0200 Martin Truebner mar...@pi-sysprog.de
wrote:
:There is lots of room in the E3xx range close to CGH and/or LGH.
:
:E310 to E312 and/or E337 thru E33D
:
:We will see next month.
--
Binyamin Dissen bdis...@dissensoftware.com
On Mon, Jun 24, 2013 at 12:55 AM, Ed Jaffe edja...@phoenixsoftware.comwrote:
The lack of AGH/SGH is a noticeable (and sometimes frustrating) gap in
the architecture.
Well, that's disappointing. I always thought the system architects were
damn close to being infallible and omnipotent :-).
Steve, all
It does look like AGH is missing. If not using register is more important
than being RENT, here is test macro program which uses MVC and AGHI:
* TEST AGH MACRO WHICH AVOIDS USING EXTRA REGISTER
* BUT IS NOT RENT
* DON HIGGINS 06/24/13
MACRO
N AGH RG,SH
MVC
I'll put in my comment. I don't think that the current z architects are
driven by how will assembler programmers use the architecture any more.
Neither are they theoretical computer architects who are wedded to an
orthogonal instruction set. To me, many of the new instruction have been
introduced
On 2013-06-24, at 08:18, Don Higgins wrote:
It does look like AGH is missing. If not using register is more important
than being RENT, here is test macro program which uses MVC and AGHI:
snip!
With a suitable work area, a RENT version could be designed.
But I suspect Charlie Brown, of
Thanks. But that makes them even more expensive to implement. Which could
be a further reason as to why they weren't.
On Mon, Jun 24, 2013 at 10:05 AM, Ed Jaffe edja...@phoenixsoftware.comwrote:
On 6/24/2013 7:42 AM, John McKown wrote:
given that most of these new instructions are likely
