From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] I can not remember if I sent this or not: MIPS-64 (sort of) notebook
Date: Fri, 20 Mar 2009 07:23:19 -0700 [thread overview]
Message-ID: <13426df10903200723h48d692e3lb1266a112c61d8f7@mail.gmail.com> (raw)
In-Reply-To: <564d7f52203aff14174c2c7cee6ab59a@quanstro.net>
On Thu, Mar 19, 2009 at 4:43 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> so, here's a silghtly controversial (maybe) suggestion. Maybe my
>> memory is wrong, but i believe the vx32 kernel is gcc-compiled. There
>> is gcc for this CPU. It might be easier to start from the vx32 kernel
>> and gcc to target this machine, rather than do a 64-bit MIPS port of
>> the plan 9 C compiler. Or not: a few of the folks on this list could
>> probably retarget in very short order (I'm not one of the,however).
>
> vx32 relies on x86 segment registers.
Let me say it differently. The way in which the plan 9 kernel code was
changed to be gcc-compilable as part of the vx32 kernel might provide
some hints as to how to change a whole plan 9 kernel. The point being,
it is not impossible to get a gcc-compilable plan 9 kernel. We used to
talk about this at LANL all the time: we called it the "evil project".
(This idea predates vx32 but it was not my idea; I will let the evil
person behind the evil project identify himself). This change would
remove "have to port&test&validate&fix&validate&... the C compiler
first" as a barrier to entry on new CPUs.
see src/vx32 in the vx32 tree.
ron
next prev parent reply other threads:[~2009-03-20 14:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 21:53 ron minnich
2009-03-19 23:14 ` Anthony Sorace
2009-03-19 23:24 ` ron minnich
2009-03-19 23:43 ` erik quanstrom
2009-03-20 14:23 ` ron minnich [this message]
2009-03-20 15:15 ` erik quanstrom
2009-03-20 15:29 ` ron minnich
2009-03-20 15:31 ` [9fans] I can not remember if I sent this or not: MIPS-64 (sort lucio
2009-03-20 16:02 ` erik quanstrom
2009-03-20 17:57 ` Charles Forsyth
2009-03-21 0:39 ` Uriel
2009-03-20 15:35 ` lucio
2009-03-20 17:11 ` [9fans] I can not remember if I sent this or not: MIPS-64 (sort of) notebook Russ Cox
2009-03-20 23:16 ` ron minnich
2009-03-20 23:52 ` James Tomaschke
2009-03-20 23:56 ` ron minnich
2009-03-21 0:06 ` Devon H. O'Dell
2009-03-20 18:28 ` Iruata Souza
2009-03-19 23:56 ` Iruata Souza
2009-03-20 2:39 ` [9fans] MIPS-64 Tim Wiess
2009-03-20 2:49 ` [9fans] I can not remember if I sent this or not: MIPS-64 (sort john
2009-03-20 3:58 ` Jack Johnson
2009-03-20 4:06 ` Jack Johnson
2009-03-20 4:06 ` Jason Gurtz
2009-03-20 4:20 ` [9fans] I can not remember if I sent this or not: MIPS-64 (sort of) lucio
2009-03-23 10:48 ` [9fans] I can not remember if I sent this or not: MIPS-64 Abhishek Kulkarni
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=13426df10903200723h48d692e3lb1266a112c61d8f7@mail.gmail.com \
--to=rminnich@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).