Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: What Happened to Interdata?
Date: Fri, 28 Jul 2023 13:38:18 +1000	[thread overview]
Message-ID: <20230728033818.GG92211@eureka.lemis.com> (raw)
In-Reply-To: <CABH=_VQMz_W41gu7w0AxQCYmAs8b9JbHWnnJNPzzasFguBBPJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

On Thursday, 27 July 2023 at 16:33:54 -0400, Paul Winalski wrote:
> On 7/27/23, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
>> Someone who's familiar with the 360 instruction set should be able to look
>> at e.g.:
>>
>> and see how compatible it is.
>
> Interdata has some data types and instructions for manipulating them
> not present in S/360.  Circular lists, for example, and instructions
> for CRC calculation.

Yes, it's possible that both Interdata and RCA/UNIVAC/ICL instruction
sets are supersets of the /360 instruction set.  The only one I still
remember is the LI (load immediate) instruction.  The /360 did the
same function with LA (load address), but IIRC that was RX (4 bytes),
while LI was RR (2 bytes).

> I didn't see anything about packed or zoned decimal support.
>
> So perhaps an extended subset of S/360.  I'd have to do a side-by-side
> comparison between this document and S/360 Principles of Operation to
> determine the level of binary program compatibility, if any.  But it
> looks like it might be better than the HitchHiker's Guide to the
> Galaxy adage:  "almost, but not quite, entirely unlike tea."

Yes, that seems reasonable.  My guess was that binary compatibility
wasn't a big issue in those days, since nearly all applications
software was written only for specific installations.  And of course
licensing issues would preclude running IBM OS on the other machines.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  reply	other threads:[~2023-07-28  3:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 19:16 Noel Chiappa
2023-07-27 20:33 ` Paul Winalski
2023-07-28  3:38   ` Greg 'groggy' Lehey [this message]
2023-07-28 16:18     ` Paul Winalski
  -- strict thread matches above, loose matches on Subject: below --
2023-07-25 23:23 [COFF] " segaloco via COFF
2023-07-26 14:38 ` [COFF] " Paul Winalski
2023-07-26 17:39   ` segaloco via COFF
2023-07-27  3:43   ` Greg 'groggy' Lehey
2023-07-27 16:30     ` Paul Winalski
2023-08-05  1:17 ` scj
2023-08-05  1:46   ` segaloco via COFF

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=20230728033818.GG92211@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=coff@tuhs.org \
    --cc=paul.winalski@gmail.com \
    /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).