From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <701581b43c25c1d9450823536223f6ce@quanstro.net> References: <13426df10903200723h48d692e3lb1266a112c61d8f7@mail.gmail.com> <701581b43c25c1d9450823536223f6ce@quanstro.net> Date: Fri, 20 Mar 2009 10:11:33 -0700 Message-ID: Subject: Re: [9fans] I can not remember if I sent this or not: MIPS-64 (sort of) notebook From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: c1643d38-ead4-11e9-9d60-3106f5b1d025 ron is suggesting is that with minimal effort the plan 9 kernel could be made to compile using gcc instead of the standard plan 9 compilers. he's right. erik's point is that once you have a kernel up, you still need to give it executables to run. this either requires porting the standard compilers to the target machine or somehow making the entire source tree compile under gcc, which would require significantly more effort than the kernel. he's also right. it all depends on what you want from plan 9. for me, the fleet plan 9 compilers save me so much time and make me so much more productive compared to waiting on gcc that on balance i'd rather spend the time to port the compiler than switch to gcc. ron is already using gcc to generate binaries to run on plan 9, though, and his use of plan 9 depends much more heavily on the "plays well with networks" aspect than it does on the fast compilation. and maybe there's no one to write the new compiler. there, using gcc might make sense. russ