From: lyricalnanoha@usotsuki.hoshinet.org (Steve Nickolas)
Subject: [TUHS] 2.11BSD cross compiler
Date: Wed, 29 Sep 2010 05:17:33 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.10.1009290516080.14504@ns305552.ovh.net> (raw)
In-Reply-To: <20100929023819.GA12919@bitmover.com>
On Tue, 28 Sep 2010, Larry McVoy wrote:
> Color me old school. I like MIPS, I worked at SGI (got married to
> an old school MIPS gal) but PDP-11 is so frigging intuitive. How
> can you not understand that instruction set? If you can't, well,
> sorry, not so much in my book. It's like a stripped down C.
>
> Come on - has anyone ever seen a better instruction set? More
> complicated, yeah, holy moly, yeah. But cleaner? We owe DEC
> for that one.
Dunno, the only instruction set I really grok is 65C02, which is by your
standards probably little more than a toy.
-uso.
next prev parent reply other threads:[~2010-09-29 3:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 5:54 Nick Downing
2010-09-29 0:24 ` Tim Newsham
2010-09-29 0:51 ` Larry McVoy
2010-09-29 2:14 ` John Cowan
2010-09-29 2:38 ` Larry McVoy
2010-09-29 2:59 ` John Cowan
2010-09-29 3:44 ` Larry McVoy
2010-09-30 4:22 ` [TUHS] PDP-8 (was: 2.11BSD cross compiler) Greg 'groggy' Lehey
2010-09-30 4:53 ` John Cowan
2010-09-30 13:50 ` Larry McVoy
2010-10-02 3:46 ` Greg 'groggy' Lehey
2010-10-02 21:03 ` Larry McVoy
2010-10-02 21:39 ` [TUHS] PDP-8 M. Warner Losh
2010-10-02 10:06 ` [TUHS] PDP-8 (was: 2.11BSD cross compiler) Wolfgang Helbig
2010-09-29 3:14 ` [TUHS] 2.11BSD cross compiler M. Warner Losh
2010-09-29 3:17 ` Steve Nickolas [this message]
2010-09-29 3:55 ` Larry McVoy
2010-09-29 4:34 ` [TUHS] 6502 and swtch, was " Warren Toomey
2010-09-29 5:13 ` Steve Nickolas
2010-09-30 17:49 ` Tim Newsham
2010-09-29 20:54 ` [TUHS] " Peter Jeremy
2010-09-29 21:34 ` Larry McVoy
[not found] <mailman.2278.1285732537.1039.tuhs@minnie.tuhs.org>
2010-09-29 16:20 ` John Finigan
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=alpine.DEB.1.10.1009290516080.14504@ns305552.ovh.net \
--to=lyricalnanoha@usotsuki.hoshinet.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).