4 ms·
I like the fact that this is happening, with a live Git repo and all. 9front is alive, sure, but bootstrapping things atop a modern compiler and a (at least pa
by rcarmo 10y ago
I like the fact that this is happening, with a live Git repo and all.
9front is alive, sure, but bootstrapping things atop a modern compiler and a (at least partially) Linux compatible ABI makes a lot of sense.
- mapcars 10y agoI didn't get it, what could gcc/clang potentially bring to Plan9?
- kruhft 10y agoPlan9 uses a different dialect of C written by Ritchie (his last compiler) than most of today's software. Also, the standard library and programming model are quite substantially different than the ANSI C model. There is something on Plan9 called APE (ANSI Posix Environment), which is kind of like WINE (an emulation layer, not an emulator or compatible ABI), for porting ANSI C apps, but it's built with a rather old version of GCC and is far from complete. Meaning, most software won't run on Plan9 without major modifications, so bringing a modern GCC/CLANG would give access to better compilation, but really there needs to be more work on APE to get more software over (lots of low hanging fruit there from what I've seen).
- pcwalton 10y agoA modern optimization pipeline.
- prestonbriggs 10y agoA lot of the fun of the Plan 9 compiler and source organization is that it doesn't optimize; instead, it compiles fast. Like the whole OS in about a minute (on a Raspberry PI). Or maybe it's 2 minutes, I don't recall. The Go folks have adopted some of the same ideas (minimal optimization and no nested include files), and they build on the experience of the Plan 9 compiler to better divide the work between the "compiler" and "linker", so we gain more from parallel make.
- microcolonel 10y agoWhole system takes about 55 minutes on a Raspberry Pi. Just the kernel takes a bit over a minute. The build speed doesn't matter much if you don't like the runtime speed.
- mveety 10y agoRuntime speed isn't much of an issue for us. There's nothing in the codebase that large or complicated enough to be slow.
- ori_b 10y agoNote that the pi is about as fast as a 233 MHz pentium 2.
- groovy2shoes 10y agoAha! That makes so much sense to me. My first PC, which I still have (runs OpenBSD nowadays), is a 350 MHz Pentium II. When I got my Raspberry Pi (a version 1 model B), running a 500 MHz ARM, I was a little taken aback by just how much slower it seemed than my old P2 box. It's got a faster clock and more RAM, how could that be? But it certainly feels slower! Do you have any sources on this? Can you perhaps link me to something that explains the differences between the ARM and the P2 that lead to such a difference in performance despite the clock speeds?
- emmelaich 10y ago
- solidsnack9000 10y agoWhat does an operating system gain from maintaining its own slightly special C compiler?
- h3ro 10y agoindependence from complex, unmaintainable, ever moving code that is mostly controlled by other people who don't share our values. for example nobody in the loonix community seems to be able to ensure that cross-compiling works.
- mveety 10y agoI don't see what you gain with either of these that's worth enough to put in that much work and add that much complexity. linuxemu is a better solution for running Linux programs, all of the added unix junk is contained. Using GCC or clang over kencc could be useful in some cases, but there, too, I don't see what fantastic gains you get. I do see major issues there like shipping GPL code with GCC and adding a massive new codebase to the tree (it wouldn't suprise me if GCC or clang's source trees were larger than 9front's). All I really see in Harvey is feature creep and trying to make Plan 9 into Linux.
- rcarmo 10y agolinuxemu has been dead for years - it's pretty much impossible to run modern 64-bit stuff in Plan9. Like, you know, a 2010-era browser...