On Tue, 20 Jan 2015 11:12:33 -0500, Farley, Peter x23353 wrote: >Jumping in a little late here, but AMODE 64 for *code* is not necessarily the >need for most business purposes. AMODE 64 for *data* is the need that I >perceive as primary. I would be well satisfied if 64-bit data storage could >be used transparently even with code running only in 31-bit storage. > Of course there are no separate AMODEs for code references and data references.
But 31-bit addressing instructions might be used for code and 64 for data. Reminds me of the diverse memory models in historic Windows. >3. ... direct I/O buffer addressing (unfortunately not usually supported by >existing HLL file semantics) ... > Pascal. But not Borland's Pascal. What ever happened to Pascal? >4. As some others have also mentioned, interfacing with Java (or any other >JVM-based language) processes passing data from 64-bit storage for HLL >business processing will be a growing requirement > >.... The ability to use direct pointer arithmetic using HLL semantics instead >of needing to use integer redefinitions of pointers to perform pointer >arithmetic would be quite helpful in such data restructuring projects. > This is intrinsic to C. Scientific Data Systems (later Xerox) hardware multiplied the index register content by the operand size when calculating effective addresses. Not the best idea. It's *so* FORTRAN! -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
