From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] I recovered 100% of the s1 src code fragments
Date: Sun, 11 May 2008 19:38:26 +1000 [thread overview]
Message-ID: <20080511093826.GB7947@minnie.tuhs.org> (raw)
In-Reply-To: <1160605.1210386850465.JavaMail.root@elwamui-norfolk.atl.sa.earthlink.net>
On Fri, May 09, 2008 at 10:34:10PM -0400, Doug Merritt wrote:
> FYI I recovered 100% of the s1 src code fragments; I presume this
> is of interest to y'all on this list, yes?
Certainy is Doug. Next time you e-mail in, I'll set you as being able to
post without a subscription. I forgot when I let your first 2 e-mails thru.
Where can we get your reassembled fragments?!
> And reading the archived messages, wow, you guys got an amazing
> amount done in a very short time! Congrats! (Boy am I glad I don't
> have to do all that by myself after all...)
I'm glad I don't have to rebuild the s1 fragments :) Thanks!
> Note that ed1.s and ed2.s are missing. Their source code simply wasn't
> in any of the fragments (which means, was not on the s1 disk image).
Damn, oh well. I should have a look at 5th Edition to see if "ed" is
in C by that stage, or still in asm form.
> NOTE: I am not sure of precisely when s1 dates to, but many of these
> source files use the "jsr r5, 0: <buffer>" calling convention that
> requires writable code segments -- did that go away sharply with the
> pdp11/20 to pdp11/45 move, or no?
Probably, but it's hard to tell. We don't have any early assembly stuff
which would date from the 11/45: it's the s1/s2 tapes, then the early
C compilers, then the "nsys" kernel which just predates 3rd Edition.
> P.S. Since doing the above, I've been working on a disassembler; it
> works ok, and emits of course 'as'-syntax asm, and accepts a markup-
> command file to allow e.g. introduction of human-chosen labels for octal
> addresses -- and I'm nearly done
> adding the ability to produce "1f" "1b" style branch labels -- I
> created a bunch of bugs in the process of doing that.
We'd love to get a copy. I started on a disassembler myself...
> P.P.S. While you're asking Ken and Dennis for more listings, ask them
> for any "Unics" PDP 7 listings they may have, too! I suspect Ken even
> has a Space Travel listing lying around, although I don't think he
> has ever mentioned it over the decades.
Shall do.
Thanks again Doug.
Warren
next prev parent reply other threads:[~2008-05-11 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 2:34 Doug Merritt
2008-05-11 9:38 ` Warren Toomey [this message]
2008-05-11 12:28 ` Warren Toomey
2008-05-12 1:47 ` Brantley Coile
2008-05-12 4:24 ` Doug Merritt
2008-05-12 15:16 ` Brantley Coile
2008-05-11 12:44 ` [Unix-jun72] when did jsr r5 stop? Warren Toomey
2008-05-11 13:53 ` [Unix-jun72] I recovered 100% of the s1 src code fragments Brad Parker
2008-05-12 4:05 ` Doug Merritt
2008-05-14 21:48 ` Tim Newsham
2008-05-15 0:35 ` Doug Merritt
2008-05-15 0:39 ` Warren Toomey
2008-05-15 0:48 ` Warren Toomey
2008-05-15 1:00 ` Doug Merritt
2008-05-15 1:10 ` Warren Toomey
2008-05-15 1:11 ` Tim Newsham
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=20080511093826.GB7947@minnie.tuhs.org \
--to=wkt@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).