🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #618456

Re: S/360 addressing, not Honeywell 200

#618456
From: Scott Lurndal
Date: Mon, 29 Jan 2018 15:14
37 lines
3291 bytes
Charles Richmond <nume...@aquaporin4.com> writes:
>On 1/27/2018 7:22 PM, Charlie Gibbs wrote:
>> On 2018-01-28, Dan Espen <dan1...@gmail.com> wrote:
>> 
>>> John Levine <jo...@taugh.com> writes:
>>>
>>>> In article <b204534e-f56c-4b29...@googlegroups.com>,
>>>>
>>>>> Memory addressing was a big issue in the original concept of
>>>>> System/360.  Small machines had simple addresses which saved
>>>>> memory, big machines had more complex addresses.  Providing space
>>>>> for a large address was wasteful in a small machine, most
>>>>> S/360 users were getting small ones.  As a compromise, IBM came
>>>>> up with the base+displacement method.
>>>>
>>>> All 360s other than the /20 used the same addressing, full 24 bit
>>>> addresses, instructions used base register plus 12 bit displacement
>>>> sometimes plus index register.  Base register 0 meant direct
>>>> addressing with the 12 bit displacement, but as far as I know that was
>>>> used only in little bits of startup and trap handler code, not in
>>>> applications.
>>>
>>> MVS applications often get system information
>>> by using an address at a fixed low storage location (CVT at 16).
>> 
>> It also lets you use Load Address to load a constant from 0 to
>> 4095 inclusive into a register (although if you're setting the
>> register to zero it's faster to subtract it from itself).
>> 
>
>How does that compare with the time for exclusive-oring the resister 
>with itself???  On the Intel 8080, that was the fastest way to zero the 
>accumulator...

That doesn't necessarily mean that the 8080 (and successors through Haswell)
actually do the xor.   Simply recognizing that the two registers are identical
would be sufficient to drive the result to zero.
Technical Details
Message-ID: <ZSGbC.1722$Ia3.59@fx44.iad>
Path: mbox-mo1.pugleaf.net!n14ni17342wmi.0!nntp.google.com!goblin2!goblin.stu.neva.ru!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post01.iad!fx44.iad.POSTED!not-for-mail
References: <65g3r9$8gg@bgtnsc03.worldnet.att.net> <p4cn29$fhm$1@dont-email.me> <p4d45k$f8e$1@dont-email.me> <b204534e-f56c-4b29-a177-dd66c2410b6d@googlegroups.com> <p4j0er$2im8$1@gal.iecc.com> <p4j5vb$u75$3@dont-email.me> <p4j8ki0ho2@news6.newsguy.com> <p4l4pn$17i$1@dont-email.me>

Show Full Headers
Complete Article Headers
X-Received: by 10.28.50.4 with SMTP id y4mr2925019wmy.1.1517238842839;        Mon, 29 Jan 2018 07:14:02 -0800 (PST)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.28.202.2 with SMTP id a2ls239257wmg.8.canary-gmail; Mon, 29 Jan 2018 07:14:01 -0800 (PST)
X-Received: by 10.28.237.21 with SMTP id l21mr2618834wmh.32.1517238841946;        Mon, 29 Jan 2018 07:14:01 -0800 (PST)
MIME-Version: 1.0
Path: mbox-mo1.pugleaf.net!n14ni17342wmi.0!nntp.google.com!goblin2!goblin.stu.neva.ru!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post01.iad!fx44.iad.POSTED!not-for-mail
X-newsreader: xrn 9.03-beta-14-64bit
Sender: scott@dragon.sl.home (Scott Lurndal)
From: scott@slp53.sl.home (Scott Lurndal)
Reply-To: sl...@pacbell.net
Subject: Re: S/360 addressing, not Honeywell 200
Newsgroups: alt.folklore.computers
References: <65g3r9$8gg@bgtnsc03.worldnet.att.net> <p4cn29$fhm$1@dont-email.me> <p4d45k$f8e$1@dont-email.me> <b204534e-f56c-4b29-a177-dd66c2410b6d@googlegroups.com> <p4j0er$2im8$1@gal.iecc.com> <p4j5vb$u75$3@dont-email.me> <p4j8ki0ho2@news6.newsguy.com> <p4l4pn$17i$1@dont-email.me>
Lines: 38
Message-ID: <ZSGbC.1722$Ia3.59@fx44.iad>
X-Complaints-To: ab...@usenetserver.com
NNTP-Posting-Date: Mon, 29 Jan 2018 15:14:01 UTC
Organization: UsenetServer - www.usenetserver.com
Date: Mon, 29 Jan 2018 15:14:01 GMT
X-Received-Body-CRC: 3907156332
X-Received-Bytes: 2721
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit