Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: coff@tuhs.org
Subject: [COFF] Re: What Happened to Interdata?
Date: Thu, 27 Jul 2023 16:33:54 -0400	[thread overview]
Message-ID: <CABH=_VQMz_W41gu7w0AxQCYmAs8b9JbHWnnJNPzzasFguBBPJw@mail.gmail.com> (raw)
In-Reply-To: <20230727191643.AE34718C079@mercury.lcs.mit.edu>

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.

Thanks for the pointer.  I took a quick look.  My knowledge of the
S/360 instruction set is very rusty at this point--it's been over 40
years since I programmed in it.

The program status word (PSW) format looks very familiar.  Both
architectures seem to support 24-bit addressing.

Interdata has some data types and instructions for manipulating them
not present in S/360.  Circular lists, for example, and instructions
for CRC calculation.

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."

-Paul W

  reply	other threads:[~2023-07-27 20:34 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 [this message]
2023-07-28  3:38   ` Greg 'groggy' Lehey
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='CABH=_VQMz_W41gu7w0AxQCYmAs8b9JbHWnnJNPzzasFguBBPJw@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=coff@tuhs.org \
    --cc=jnc@mercury.lcs.mit.edu \
    /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).