From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] pdp-11 assembly as a hll?
Date: Wed, 14 Feb 2018 09:41:25 +0100 [thread overview]
Message-ID: <08FA5285-3A14-491E-B723-B40AE85B4151@planet.nl> (raw)
>> I was wondering what it would take to convert the v6/v7 basic program
>> into something that can be run today.
>
> Hmmm... If it were C-generated then it would be (somewhat) easy, but it's
> hand-written and hand-optimised... You'd have to do some functional
> analysis on it e.g. what does this routine do, etc.
>
>> Its 2128 lines. It doesn't have that fun instruction in it :)
>
> I know! Say ~2,000 lines, say ~100 people on this list, distributed
> computing to the rescue! That's only 20 lines each, so it ought to be a
> piece of cake :-)
I'm up for that! However, only if the resulting C program can be compiled/run
on a V6/PDP11 again.
Let's assume that reverse engineering a subroutine of 20 lines takes
an hour. That then makes for 100 hours. If 10 people participate and
contribute one hour/routine per week, it will be done by May.
However, the initial analysis of the code architecture is a (time) hurdle.
Paul
PS: the Fortran66 of V6 is also assembler only...
next reply other threads:[~2018-02-14 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 8:41 Paul Ruizendaal [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 13:15 Noel Chiappa
2018-02-14 1:08 Warner Losh
2018-02-14 3:18 ` Dave Horsfall
2018-02-14 5:12 ` Warner Losh
2018-02-14 6:43 ` Dave Horsfall
2018-02-14 7:27 ` Bakul Shah
2018-02-14 7:28 ` Ian Zimmerman
2018-02-14 16:03 ` Paul Winalski
2018-02-14 16:56 ` Warner Losh
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=08FA5285-3A14-491E-B723-B40AE85B4151@planet.nl \
--to=pnr@planet.nl \
/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).