From: bakul at bitblocks.com (Bakul Shah)
Subject: [COFF] In Memoriam: Jay W. Forrester, happy birthday Gene Amdahl, and LSD
Date: Mon, 18 Nov 2019 10:45:13 -0800 [thread overview]
Message-ID: <9FA0B3E9-0E66-4724-BF6C-AF60EF5EE784@bitblocks.com> (raw)
In-Reply-To: <CAC20D2Nmxo+5LJpYSVDJ_Cq3cSxS4hVop312opA9AYnckhgrjw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Are you guys talking about “A formal description of System/360” by Falkoff, Iverson and Sussenguth? It uses an APL like notation but not exactly a S/360 emulator in APL! Much more concise than the S/360 POP.
http://www.cs.trinity.edu/~jhowland/class.files.cs2321.html/falkoff.pdf
>> On Nov 18, 2019, at 8:43 AM, Clem Cole <clemc at ccc.com> wrote:
>
>
>
>> On Sun, Nov 17, 2019 at 12:14 AM Dave Horsfall <dave at horsfall.org> wrote:
>> On Sat, 16 Nov 2019, Peter Jeremy wrote:
>>
>> > More than just the instruction set - IBM published a formal description
>> > of the S/360 (in APL in the IBM Systems Journal issue that announced the
>> > S/360). The S/360 was (I believe) the first case where a company
>> > announced a computer architecture (rather than an implementation) and
>> > implementations were expected to precisely comply with the architecture
>> > (no more finding undocumented instructions and side-effects and writing
>> > code that depended on them). This meant that clone makers could build a
>> > clone that accurately emulated a S/360.
>>
>> Ah, I'd forgotten about the APL documentation; thanks! Talk about giving
>> away the keys to the kingdom: Amdahl, Fujitsu, Hitachi...
>
> The cat was already out and poking around with the publishing of: IBM 360 Principles of Operation, DOC A22-6821-0. The APL version of spec just gave it more area to roam.
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191118/b9b188d2/attachment.html>
next prev parent reply other threads:[~2019-11-18 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 21:54 dave
2019-11-15 22:26 ` krewat
2019-11-15 22:42 ` dave
2019-11-16 7:23 ` peter
2019-11-16 16:25 ` clemc
2019-11-17 5:14 ` dave
2019-11-18 16:42 ` clemc
2019-11-18 18:45 ` bakul [this message]
2019-11-18 19:19 ` clemc
2019-11-19 20:21 ` peter
2019-11-19 23:17 ` cym224
2019-11-21 19:48 ` dave
2019-11-15 23:19 ` clemc
2019-11-15 23:47 ` krewat
-- strict thread matches above, loose matches on Subject: below --
2018-11-15 22:33 dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9FA0B3E9-0E66-4724-BF6C-AF60EF5EE784@bitblocks.com \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).