The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] head/sed/tail (was The Unix shell: a 50-year view)
Date: Thu, 15 Jul 2021 15:28:32 -0400	[thread overview]
Message-ID: <CAC20D2PEG82MS9CWQkhfX2Ud7ZegRVDfg-_T2NG4aT9++H3KdQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NPMovqkKLahRKopt5y4mPQrmpNi__RrjtRw6cowmwszQ@mail.gmail.com>

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

g/Synder/s//Snyder/ -- sigh....
ᐧ

On Thu, Jul 15, 2021 at 3:27 PM Clem Cole <clemc@ccc.com> wrote:

> The 'second' C compiler was a PDP-10 and Honeywell (36-bit) target Alan
> Synder did for his MIT Thesis.
> It was originally targeted to ITS for the PDP-10, but it ran on Tops-20
> also.
>
> My >>memory<< is he used a 7-bit Character, ala SAIL, with 5 chars stored
> in a word with a bit leftover.
>
> You can check it out:  https://github.com/PDP-10/Snyder-C-compiler
>
> I believe that C compiler Nelson is talking about I believe is actually
> Synder's that Jay either ported from ITS  or WAITS.
>
> We had some form of the Synder compiler on the PDP-10's at CMU in the late
> 1970s.
> It was either Mike Accetta or Fil Aleva that wrote a program to read
> PDP-10 backup tapes, that I updated to deal with TOPS-20/TENEX 'dumper'
> format which was similar/only different.
> ᐧ
>
> On Thu, Jul 15, 2021 at 3:03 PM Norman Wilson <norman@oclsc.org> wrote:
>
>> Nelson H. F. Beebe:
>>
>>   P.S. Jay was the first to get Steve Johnson's Portable C Compiler,
>>   pcc, to run on the 36-bit PDP-10, and once we had pcc, we began the
>>   move from writing utilities in Pascal and PDP-10 assembly language to
>>   doing them in C.
>>
>> ======
>>
>> How did that C implementation handle ASCII text on the DEC-10?
>> Were it a from-scratch UNIX port it might make sense to store
>> four eight- or nine-bit bytes to a word, but if (as I sense it
>> was) it was C running on TOPS-10 or TOPS-20, it would have had
>> to work comfortably with DEC's convention of five 7-bit characters
>> (plus a spare bit used by some programs as a flag).
>>
>> Norman Wilson
>> Toronto ON
>>
>

[-- Attachment #2: Type: text/html, Size: 3927 bytes --]

  reply	other threads:[~2021-07-15 19:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 19:01 Norman Wilson
2021-07-15 19:27 ` Clem Cole
2021-07-15 19:28   ` Clem Cole [this message]
2021-07-15 19:34   ` Warner Losh
2021-07-16  7:38     ` arnold
2021-07-16 16:09       ` Warner Losh
2021-07-16  8:05   ` Lars Brinkhoff
2021-07-16 14:19     ` Clem Cole
2021-07-17  0:34       ` Charles Anthony
  -- strict thread matches above, loose matches on Subject: below --
2021-07-18 20:07 Douglas McIlroy
     [not found] <CAKH6PiW58PDPb5HRi12aKE+mT+O8AjETr9R51Db6U3KcEp_KkA@mail.gmail.com>
2021-07-16 14:17 ` Nelson H. F. Beebe
2021-07-16 16:13   ` Theodore Y. Ts'o
2021-07-16 12:09 Douglas McIlroy
2021-07-16 14:32 ` Bakul Shah
2021-07-15 22:26 Nelson H. F. Beebe
2021-07-15 23:18 ` Jim Davis
2021-07-16  0:02   ` John Floren
2021-07-16  1:02     ` Nelson H. F. Beebe
2021-07-16  8:27     ` Lars Brinkhoff
2021-07-16 15:28       ` John Floren
2021-07-16  0:02 ` Clem Cole
2021-07-16  0:25   ` Nelson H. F. Beebe
2021-07-16  8:50     ` Lars Brinkhoff
2021-07-15 22:00 Douglas McIlroy
2021-07-15 22:12 ` John Cowan
2021-07-15 21:26 Paul Ruizendaal
2021-07-15 16:54 Nelson H. F. Beebe
2021-07-15 15:44 Norman Wilson
2021-07-15  2:38 Douglas McIlroy
2021-07-15  4:19 ` arnold
2021-07-15  4:25   ` Adam Thornton
2021-07-15  7:20   ` Thomas Paulsen
2021-07-15 14:28 ` Theodore Y. Ts'o
2021-07-15 22:29 ` Bakul Shah

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=CAC20D2PEG82MS9CWQkhfX2Ud7ZegRVDfg-_T2NG4aT9++H3KdQ@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=norman@oclsc.org \
    --cc=tuhs@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).