I'm in the middle of building this new compiler. Anyone here tried it and would like to share your experience? Does it break building of existing packages?

Some. glib-1.2.10 and gnome-terminal-2.6.0 were the only ones that mattered to me. Also it doesn't create the same shared libraries so some things that were compiled against older versions of gcc will not run unless the shared libraries are kept around for compatibility

Thanks for replying. Hell, I couldn't even get a successful build without tinkering with the source. The libiberty tree's configure script does not detect stdlib.h and some other files which are installed which breaks the whole build.

Which older versions are you referring to?

Well some things need the shared libraries from gcc-2.9 (flash) and some things need gcc-3.2/3.3, depending what they were compiled with. Last week I built Bleeding Edge Linux From Scratch which used gcc3.4 checked out through cvs. Bleeding edge uses glibc-2.3.4 and builds on the linux-2.6 kernel headers, which may be why I didn't experience your problems with libiberty. I had no problem compiling gcc-3.4 or any of the packages in Bleeding Edge, it was when I started to build on top of the basic system I started to have problems. Firefox wouldn't run as there was a shared library missing (I forget which one, libstd- something) and the Firefox-0.8 source tarball wouldn't build with gcc-3.4 so I pulled the current source with cvs and that built and ran with no problems. To get glib-1.2.10 and the gnome terminal to build I had to install gcc-3.3.1 in /opt and use that, which was less than ideal but needs must. The kernel built no problem with gcc-3.4. It runs fine too. The only reason I don't use that version of Linux from scratch as my default boot is I can't get my printers to work. I think the problem there is with udev, which is a whole different subject.