From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Need a new PDP-11 or VAX?
Date: Sat, 27 Apr 2013 20:57:36 -0700 [thread overview]
Message-ID: <20130428035736.GA1001@bitmover.com> (raw)
In-Reply-To: <20130428013911.GD24560@mercury.ccil.org>
On Sat, Apr 27, 2013 at 09:39:11PM -0400, John Cowan wrote:
> Larry McVoy scripsit:
>
> > What I'd like is a new 64 bit PDP-11.
>
> With a 16-bit instruction stream still, or with wider instructions and
> more registers, almost but not quite entirely unlike the Vax?
Ideally with 32 bit ints, 64 bit longs, 32 or 64 bit pointers in the
compiler, obviously more registers, and nothing like the vax. Maybe
I'm too dumb to get it but I never warmed up to the vax.
National 32032 was closer.
> De plichten van een docent zijn divers, John Cowan
> die van het gehoor ook. cowan at ccil.org
> --Edsger Dijkstra http://www.ccil.org/~cowan
Much thanks for a .sig that is in Dutch, brings back some memories.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2013-04-28 3:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 21:26 Dave Horsfall
2013-04-27 22:41 ` Larry McVoy
2013-04-27 23:53 ` Dave Horsfall
2013-04-28 0:12 ` Ronald Natalie
2013-04-28 1:39 ` John Cowan
2013-04-28 3:38 ` Nick Downing
2013-04-28 3:48 ` Larry McVoy
2013-04-28 3:57 ` Larry McVoy [this message]
2013-04-28 5:57 ` John Cowan
2013-04-28 5:34 ` [TUHS] curmudgeon credit Aharon Robbins
2013-04-28 7:08 ` Nick Downing
2013-05-14 6:11 ` Aaron J. Grier
2013-05-14 6:52 ` emu
2013-05-14 7:51 ` David Evans
2013-04-28 16:28 ` Larry McVoy
2013-04-28 7:45 ` [TUHS] Need a new PDP-11 or VAX? Peter Jeremy
2013-04-28 10:50 ` Ronald Natalie
2013-04-28 0:15 ` Ronald Natalie
[not found] <mailman.3.1367200802.17183.tuhs@minnie.tuhs.org>
2013-04-29 23:19 ` David Barto
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=20130428035736.GA1001@bitmover.com \
--to=lm@bitmover.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).