From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] s1 fragments are now in the svn repository
Date: Thu, 15 May 2008 12:34:26 +1000 [thread overview]
Message-ID: <20080515023426.GA5082@minnie.tuhs.org> (raw)
In-Reply-To: <20080515014608.GA3761@minnie.tuhs.org>
On Thu, May 15, 2008 at 11:46:08AM +1000, Warren Toomey wrote:
> I have just spent some time reconciling the differences between Doug's s1
> fragment reconstruction and mine: we both had roughly the same # of errors,
> and having the other's work was great. The repository has all the files in
> src/cmd. I have not tried to assemble all of them yet, so any reports here
> would be good. Remember, the C files will not compile with the existing
> compiler.
Most of the files assemble, and I've created a "mak" script to do so under
1st Edition. C files are out, they need a later language than the last1120c
compiler. We are missing some files for bas. The dc and form source uses
"new" instructions like mul and ashc, which the existing V1 "as" binary
does not understand, but the assembler in source code does understand,
so these may still be assembled.
Warren
next prev parent reply other threads:[~2008-05-15 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 1:46 Warren Toomey
2008-05-15 2:34 ` Warren Toomey [this message]
2008-05-15 3:03 ` [Unix-jun72] Observations about this ancient C dialect Doug Merritt
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=20080515023426.GA5082@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).