From: Tim Wiess <tim@nop.cx>
To: 9fans@9fans.net
Subject: Re: [9fans] MIPS-64
Date: Thu, 19 Mar 2009 19:39:11 -0700 [thread overview]
Message-ID: <129e77e6390963389805d685b070a434@akira.nop.cx> (raw)
In-Reply-To: <d1c554290903191656n2e22e290n271156c8d2248a7@mail.gmail.com>
Yes I started on working the toolchain a couple years ago, based on
some earlier work done at the labs. Development stalled due to other
work at the time and I never got back to it.
But it's on sources (tim/4acl.tgz) if anybody wants to pick it up.
I'm happy to provide any help.
tim
> tim weiss started work on kencc mips64 port and I started (w/o the
> compiler) playing with Plan 9 on mips64 based on the old carrera port.
>
> the stupid initial code is at http://src.oitobits.net/9sgi
>
> On Thu, Mar 19, 2009 at 8:24 PM, ron minnich <rminnich@gmail.com> wrote:
>> On Thu, Mar 19, 2009 at 4:14 PM, Anthony Sorace <anothy@gmail.com> wrote:
>>> i was looking at this a week or two ago, trying to find an ARM or MIPS
>>> laptop to play with. my first question was whether the "missing" parts
>>> of the MIPS instruction set are things that our compilers currently
>>> generate; SoC (oh, and my day job) ramped up before i could find the
>>> list of missing instructions. any idea?
>>>
>>> getting quotes or delivery in the US seemed tricky, too.
>>
>> 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).
>>
>> ron
>>
>>
>
>
>
> --
> iru
next prev parent reply other threads:[~2009-03-20 2:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 21:53 [9fans] I can not remember if I sent this or not: MIPS-64 (sort of) notebook 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
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 ` Tim Wiess [this message]
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=129e77e6390963389805d685b070a434@akira.nop.cx \
--to=tim@nop.cx \
--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).