Matthew Green says he is ready to switch Sparc, Sparc64, i386 & Alpha ports to using GCC3.3.1 by default. He’s uploaded 4 snapshots, all cross compiled from i386-netbsd. However, there appears to be work involved with fixing approximately 193 broken packages, BSDForums reports.
GCC 3.3.1 Switch Coming Soon on NetBSD
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
This I like.
FreeBSD made the switch to 3.x with their 5.x series and I rather like it
.
NetBSD 2.0 seems to be a huge step forward, kernel scheduled entities, better SMP for more platforms, gcc 3.x, topdown VM, non-executable stack & heap on some platforms. Of course, all technologies need testing, so if you have a spare box somewhere…
got some pointers to the netbsd 2.0 info? i havnt read anything on netbsd integrating kse from freebsd. i couldnt find anything on google either…
Hark! What is this NetBSD 2.0 you speak of? I’ve only seen 1.6.1.
Just compiled the NetBSD kernel with gcc 3.3.1 , it gave 4 warnings , the -Werror flag had to be removed. And it worked nicely.
Oh.. try compiling the Linux kernel with e.g. -Wall , you get _tons_ of warning. NetBSD throws in the -Werror flag, and treats all warnings as errors
df: http://www.netbsd.org/Changes/changes-2.0.html is a list of major changes between 1.x and the upcoming 2.0 release.
anonymous: no, NetBSD 2.0 is not released yet, and it will probably take a while till it is released. But you can use a snapshot or -current if you want to try new features. But please be aware that -current is under heavy development, so don’t expect it to be stable.
Hmmm… Perhaps OpenBSD will include GCC 3.x and some of the other nifty NetBSD features (those not migrated over from OpenBSD in the first place, of course) soon. When it does, I’m going to have to give it a long, hard look and decide on whether to switch back from FreeBSD 5.x.
@df: NetBSD isn’t importing KSE from FreeBSD. The NetBSD approach is a direct implementation of the Scheduler Activation paper by Anderson.
KSE is based on SA, but with some modifications.
don’ think so
openbsd developpers are really against any evolution to gcc3 because it is more slower (twice or more) than gcc 2.95.3 and some other things
see
this thread on misc@
http://marc.theaimsgroup.com/?l=openbsd-misc&m=104425144501692&w=2
http://www.deadly.org/article.php3?sid=20030817203333
don’ think so
openbsd developpers are really against any evolution to gcc3 because it is more slower (twice or more) than gcc 2.95.3 and some other things
Do you know what the slowness is concerning? the compiling and since most people don’t sit in front of the computer staring whilst something is compiling, you point is mute. The extra time compiling can are outweighed in comparsion to the cleaner code produced by the 3.x series, especially on the non-x86 platforms.
As for the links you provided, they represent on a few whingers and whiners. Unlike you, I would rather wait and see what the the core programmers have to say.
The OpenBSD Project doesn’t like gcc. They would like to replace gcc with Plan9’s C compiler but there are license problems.
on a dual i386 box and it flies… an it didn’t crashed while using the MP Kernel too 🙂
Hope they will choose GCC 3.3.1 for netbsd/macppc soon
-A
I wanted to say ia32(x86) of course
we use k++/gkk instead of c++/gcc.
jemals!
Till
Why k++/gkk? I would rather think about z++/gzk.
For the rest I find it nice to see the progress NetBSD is making, I’m really looking forward to 2.0 (at least if it includes XFree 4.3)
I haven’t been able to get NetBSD running on my dell latop, nor 1.5, nor 1.6, nor 1.6.1. The kernel freezes on first boot . I am really looking forward for the people of NetBSD to give better support for the dell inspiron series, it is a nice OS, maybe 2.0 will finally make it possible.
actually we also use ü++ and ä++ from time to time, yet I love digging into some old fashioned ß++
However, unlike in the US, we don’t code in Borland Delphin, we prefer the Walfisch programming language.
(See http://www.walfisch.de)
jemals!
Till