| |||||||||||||
|
| |||||||||||||
Building the Debian archive with GCC 4.4Building the Debian archive with GCC 4.4Posted Sep 15, 2008 22:43 UTC (Mon) by JoeBuck (subscriber, #2330)Parent article: Building the Debian archive with GCC 4.4 Martin's been doing this kind of work for some time, and it helps greatly in making sure that GCC, when released, is of high quality. Building nearly 10k packages on multiple platforms and documenting all of the bugs found is a huge task, and we're all lucky that he's been willing to take it on. The bug level he's finding is normal for this stage of GCC development (early in stage 3, the bug fix phase); by the time there's a GCC 4.4.0 release, you can expect these problems to be fixed.
(Log in to post comments)
Building the Debian archive with GCC 4.4 Posted Sep 15, 2008 22:46 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]
Are you getting similar feedback from Fedora maintainers on the rawhide branch as well?
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 0:02 UTC (Tue) by JoeBuck (subscriber, #2330) [Link] I haven't seen anyone other than Martin regularly post reports of the form "we tried to build a complete distro with a bleeding-edge unreleased GCC, here's what happened".In practice, once you can build all of Debian on many platforms, the same's likely to be true of other GNU/Linux distros. It would be useful to get reports like this from the BSD distros; often GCC support under BSD suffers because we don't get as much early testing.
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 1:09 UTC (Tue) by cyrus (guest, #36858) [Link]
I think at least the FreeBSD Project decided not to switch to a GPLv3 compiler. Right now, they're sticking with GCC 4.2.x, so it's unlikely that we'll see any report about upcomming GCC versions from them.
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 3:32 UTC (Tue) by JoeBuck (subscriber, #2330) [Link] Any user is free to contribute tests, even if the distro itself chooses (for whatever reason) to stick with an older compiler version.Doing so will make life easier when people change their minds in a couple of years (especially people who need a C++0x compiler).
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 7:37 UTC (Tue) by coriordan (guest, #7544) [Link]
hmmm. Got a link to where the FreeBSD folk discussed this or where the decision was announced?
Thanks.
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 16:41 UTC (Tue) by sbergman27 (subscriber, #10767) [Link]
"""
Got a link to where the FreeBSD folk discussed this or where the decision was announced? """
A link would be interesting. But talk is cheap. What compiler is currently in the FreeBSD 8 cvs tree?
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 18:58 UTC (Tue) by bkoz (guest, #4027) [Link]
FWIW, Here's an example of one user (Gerald Pfeifer) testing GCC-head on more-recent FreeBSD (6.3.x).
http://gcc.gnu.org/ml/gcc-testresults/2008-09/msg01375.html
The GCC team is accepting patches that improve GCC support on new BSDs. I have no visibility into the FreeBSD toolchain discussions.
Building the Debian archive with GCC 4.4 Posted Sep 16, 2008 23:54 UTC (Tue) by JoeBuck (subscriber, #2330) [Link] Gerald's not only a user, he's a long-time GCC developer, SC member and gcc.gnu.org webmaster, and he's been giving the BSDs a lot of love despite working for a Linux-based org during the day.But running GCC's regression test suite, while useful and important, isn't as big a job as using the compiler to build an entire distribution (including ports trees). That's what Martin's been doing for Debian. Volunteers welcome.
Building the Debian archive with GCC 4.4 Posted Sep 20, 2008 14:38 UTC (Sat) by mdomsch (subscriber, #5920) [Link]
Note: Jakub Jelinek did a full Fedora Rawhide rebuild using prerelease gcc 4.3 back in January 2008, looking for compiler bugs, source changes needed due to stricter C++ and/or bits rearranged in header files, and resultant packaging changes.
https://www.redhat.com/archives/fedora-devel-list/2008-Ja...
Of those failures, 4 were GCC internal compiler errors, which he filed bugs in gcc's tracker and noted the bugs in his report.
|
|
||||||||||||