GCC4 Builds on Haiku-Files

Blog post by Sikosis on Thu, 2009-04-30 05:20

Just thought we'd let you know that, Haiku-Files is now hosting GCC4 builds of Haiku in both RAW and VM image formats.

You can obtain these builds in the usual directories and we've updated the RSS feeds as well.

We've also fixed the VMX file that is distributed with the pre-alpha images to have the correct virtual hard disk name. Sorry for this oversight, I wasn't aware of it, until I was playing around with VMware Fusion last night.

Comments

Re: GCC4 Builds on Haiku-Files

Nice will check wen I get back home (with HaikuOnAStick ;) )

Re: GCC4 Builds on Haiku-Files

Images are they only showed when they are finnished?

Re: GCC4 Builds on Haiku-Files

Yep -- new builds are kicked off at 23:00 GMT, built and uploaded within about 30-40 minutes.

Re: GCC4 Builds on Haiku-Files

I've never tried the GCC4.x builds. Other than lack of binary compatibility and easier porting of external code, what is the biggest difference between 2.9x and 4.x?

Are the binaries smaller/larger?

Is the performance better/worse?

I've only built the official 2.9x builds, but never tried building a 4.x version. Inquiring minds need to know!!!

Re: GCC4 Builds on Haiku-Files

I tried the GCC4 built from yesterday (30.04.2009)
and it works.

Cannot find any difference, only some programs are missing, like vlc.
Maybe it is not working yet with GCC4 (Idontknow).

Also i cannot mount my windows partitions with the GCC4 built.
With the 2.95 GCC i can mount my windows partitions.

I even managed to get this built on my SD-Flash Card reader and I even got it booting on my Centrino core 2 Duo Notebook. Unfortunatelly it will go to the 4 image only and then to the KDL. Dont know how to report a bug, maybe someone can post me a link...

After typing "cont" command it will go up to the rocket and then I can still use the debugger, but it wont show the GUI.

At least there is some hope now.

Re: GCC4 Builds on Haiku-Files

VLC has no GCC4 port for Haiku yet. In fact, I believe the VLC provided on GCC2 Haiku images are really just BeOS builds still, unless they have been replaced with a Haiku version recently.

What type of windows partitions are you mounting?

If they are NTFS, then that would suggest that the gcc2 builds have GPL_ADDONS enabled (which they certainly should not), if they are FAT, then I'm a bit surprised, as that would suggest the Haiku FAT filesystem doesn't work in gcc4, but does in gcc2. That needs to be investigated.

GCC4 builds (or GCC2 hybrid builds with additional GCC4 libraries) are definitely required if you want run any GCC4-only software. There are now a few things floating around that require GCC4.

I personally use GCC4 Haiku for lots of recent porting work I've been doing - as I've been messing with stuff that simply doesn't compile with GCC2. As a result, if it uses C++, it also will not run on a GCC2-only Haiku once I'm done building it. There is at least one app I ported, that required GCC4 for C99 compliance, but was C-only, and so it still did run in GCC2 Haiku :)

Re: GCC4 Builds on Haiku-Files

Bruno Brocoli wrote:

I even managed to get this built on my SD-Flash Card reader and I even got it booting on my Centrino core 2 Duo Notebook. Unfortunatelly it will go to the 4 image only and then to the KDL. Dont know how to report a bug, maybe someone can post me a link...

http://dev.haiku-os.org/

Just in case you haven't checked, does the "sc" command show anything ?

Re: GCC4 Builds on Haiku-Files

Zenja wrote:

I've never tried the GCC4.x builds. Other than lack of binary compatibility and easier porting of external code, what is the biggest difference between 2.9x and 4.x?

Are the binaries smaller/larger?

Is the performance better/worse?

Well there's been alot of optimization improvements between gcc 2.95 and gcc 4.x, it may not show so much in the actual operating system (particularly such a low latency os like Haiku) however in cpu intensive programs there should be a noticeable difference. Also note that unless I'm mistaken, Haiku defaults to using -O2 optimization when building and some of the newer optimizations are only activated in -O3. Also compiling for your particular cpu (-march and -msseX) can yield further efficiency, same goes for things like profile-guided optimization.

Apart from optimizations there's code that can't be easily ported using an old compiler like 2.95 so my guess is that when Haiku 1.0 is released the hybrid version will be the most likely candidate and then with time the 2.95 support will slowly be edged out as more and more software will be (re)compiled using the newer gcc toolchains.