From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] speaking of early C compilers
Date: Mon, 27 Oct 2014 22:06:29 -0400 [thread overview]
Message-ID: <FB9C423A-9EDD-4F86-BE91-A79C9E57D216@ccc.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1410281157190.57132@aneurin.horsfall.org>
yes: http://repository.cmu.edu/cgi/viewcontent.cgi?article=3241&context=compsci
I had a 60 running v7 years later. we also toyed with adding CSV/CRET but never did it because we got an 11/70
> On Oct 27, 2014, at 9:09 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
>> On Mon, 27 Oct 2014, Clem Cole wrote:
>>
>> [...] because the CMU 11/40E had special CSV/CRET microcode which we
>> could not use on the 11/34.
>
> The 40E had microcode whilst the vanilla 40 didn't? I thought only the 60
> was micro-programmable; I never did get around to implementing CSV/CRET on
> our 60 (Digital had a bunch of them when a contract with a publishing
> house fell through).
>
>> The other things for those days, that has not yet been brought up was
>> the famous "NUXI" problem. The PDP-11 byte swapping was idemic in the
>> code. When the first ports to system that were not the same
>> "endianess" came about - you would find strange things in memory.
>
> Reminds me of the time when I used 2-char constants in case statements; my
> boss yelled at me.
>
> --
> Dave Horsfall (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
> http://www.horsfall.org/spam.html (and check the home page whilst you're there)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141027/2e8be232/attachment.html>
next prev parent reply other threads:[~2014-10-28 2:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:32 Jason Stevens
2014-10-27 13:03 ` Brantley Coile
2014-10-27 13:34 ` Ronald Natalie
2014-10-27 13:40 ` random832
2014-10-27 14:04 ` Clem Cole
2014-10-27 15:04 ` Dave Horsfall
2014-10-27 17:09 ` scj
2014-10-27 20:35 ` Ronald Natalie
2014-10-27 21:34 ` Clem Cole
2014-10-28 1:09 ` Dave Horsfall
2014-10-28 2:06 ` Clem Cole [this message]
2014-10-28 12:22 ` Ronald Natalie
2014-10-28 12:42 ` Clem Cole
2014-10-28 13:03 ` Ronald Natalie
2014-10-28 22:02 ` John Cowan
2014-10-27 13:46 Noel Chiappa
2014-10-27 13:54 Jason Stevens
2014-10-27 14:48 Noel Chiappa
2014-10-27 15:09 ` Ronald Natalie
2014-10-27 15:13 ` Dave Horsfall
2014-10-27 16:52 ` Dan Cross
2014-10-27 15:48 Noel Chiappa
2014-10-27 16:25 ` Dave Horsfall
2014-10-28 0:16 ` John Cowan
2014-10-27 16:50 Norman Wilson
2014-10-27 18:16 Nelson H. F. Beebe
2014-10-28 1:55 Jason Stevens
2014-10-28 12:52 ` Ronald Natalie
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=FB9C423A-9EDD-4F86-BE91-A79C9E57D216@ccc.com \
--to=clemc@ccc.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).