From: chet.ramey@case.edu (Chet Ramey)
Subject: [TUHS] origins of void*
Date: Sun, 5 Nov 2017 16:08:01 -0500 [thread overview]
Message-ID: <dd652f35-b345-49c0-b77c-58978aad6ee8@case.edu> (raw)
In-Reply-To: <C8D56DC7-BB40-422F-8A0F-E18F3E854A66@ccc.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On 11/5/17 3:12 PM, Clem cole wrote:
> IIRC Leffler and Shannon had something
> for a compiler backend at Case when they started their PE port, although
> they had to do some hacking as the model they had was different from any
> previous PE (they had to deal with a number of 7 bit and 24 bit issues). I
> believe one of the attractions to the PE was they model the Research folks
> had access was 32 bits and the PDP-11 was 16. I’ll try to ask Sam with
> what they started.
It was a Harris /6 (I don't know how much that has in common with any PE
model), Sam started with Johnson's PCC, and it was apparently a huge PITA.
I have a copy of his thesis describing the work.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet at case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2017-11-05 21:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 10:19 Paul Ruizendaal
2017-11-05 9:48 ` Clem Cole
2017-11-05 10:06 ` arnold
2017-11-05 13:20 ` Ron Natalie
2017-11-05 15:14 ` Warner Losh
2017-11-05 17:53 ` Clem cole
2017-11-05 18:29 ` Steve Simon
2017-11-05 20:12 ` Clem cole
2017-11-05 21:08 ` Chet Ramey [this message]
2017-11-05 21:38 ` Clem cole
2017-11-05 21:53 ` Steve Simon
2017-11-05 20:44 ` Paul Ruizendaal
2017-11-05 21:06 ` Warner Losh
2017-11-06 7:24 ` arnold
2017-11-06 15:02 ` Warner Losh
2017-11-06 21:46 ` [TUHS] origins of void* -- Apology! Steve Johnson
2017-11-06 22:18 ` Warner Losh
2017-11-07 0:25 ` Ron Natalie
2017-11-07 0:34 ` Arthur Krewat
2017-11-07 0:36 ` Ron Natalie
2017-11-07 1:09 ` Bakul Shah
2017-11-07 1:55 ` Ron Natalie
2017-11-08 17:44 ` Ralph Corderoy
2017-11-08 19:56 ` Ron Natalie
2017-11-08 20:39 ` Don Hopkins
2017-11-08 20:42 ` Ron Natalie
2017-11-08 20:47 ` Don Hopkins
2017-11-08 20:48 ` Don Hopkins
2017-11-08 20:43 ` Don Hopkins
2017-11-08 20:43 ` Clem Cole
2017-11-08 20:45 ` Warner Losh
2017-11-09 6:33 ` Lars Brinkhoff
2017-11-08 20:50 ` Steve Nickolas
2017-11-08 21:25 ` Bakul Shah
2017-11-09 6:37 ` Lars Brinkhoff
2017-11-09 7:14 ` Don Hopkins
2017-11-09 7:44 ` Lars Brinkhoff
2017-11-10 23:43 ` [TUHS] PowerPC, bit twiddling - was " Toby Thain
2017-11-10 23:58 ` Ralph Corderoy
2017-11-05 15:43 [TUHS] origins of void* Noel Chiappa
2017-11-05 16:58 ` Steve Johnson
2017-11-06 0:37 Doug McIlroy
2017-11-06 4:59 ` Steve Johnson
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=dd652f35-b345-49c0-b77c-58978aad6ee8@case.edu \
--to=chet.ramey@case.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).