9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] MMIXWare Plan 9
Date: Mon,  9 Mar 2009 16:12:23 -0400	[thread overview]
Message-ID: <3aaafc130903091312l4a1503d3j1a4cd678cf8d1739@mail.gmail.com> (raw)
In-Reply-To: <509071940903091257k285ef2d0l560a6857811b597d@mail.gmail.com>

On Mon, Mar 9, 2009 at 3:57 PM, Anthony Sorace <anothy@gmail.com> wrote:
> i'm not sure whether the MMIX stuff was a fresh effort or an extension

MMIX is totally new, a more modern, RISC-y assembly language. Knuth
worked with Hennessy on it, and it shows (not in a bad way, of
course). AFAIK it's all new code since it's so drastically different.

> of the MIX code, but it might be worth noting that someone (Charles, i
> think) ported MIX years ago. perhaps a useful starting point.
>
> On 2009-03-09, Paweł Lasek <pawel.lasek@gmail.com> wrote:
>> On Mon, Mar 9, 2009 at 14:35, xiantingmanbu <xiantingmanbu@gmail.com> wrote:
>>> How to port MMIXWare into Plan 9?  Has anyone done it?
>>>
>>  Porting wouldn't be hard. I don't remember the code right now (will
>> look into it when I get home) but probably the only thing you would
>> have to change would be mmap() to segattach(), or even simple
>> malloc()-style allocation. Knuth is rather old fashioned, so it might
>> actually work out of the box with APE, and with little changes with
>> native libs.
>> --
>> Paweł Lasek
>> On #lisp@freenode.net
>> "<schme> But the systems seem so darned complicated. I see the wife
>> unit here sitting around with winXP and it seems very complicated."
>>
>>
>
>



  reply	other threads:[~2009-03-09 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 14:35 xiantingmanbu
2009-03-09 17:16 ` Paweł Lasek
2009-03-09 19:57   ` Anthony Sorace
2009-03-09 20:12     ` J.R. Mauro [this message]
2009-03-10  3:08 ` Lee Duhem

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=3aaafc130903091312l4a1503d3j1a4cd678cf8d1739@mail.gmail.com \
    --to=jrm8005@gmail.com \
    --cc=9fans@9fans.net \
    /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).