Linked by Thom Holwerda on Tue 28th Mar 2006 21:15 UTC, submitted by anonymous
Debian and its clones Over the last two weeks, Debian developer Martin Michlmayr compiled the whole Debian archive on a quad-core MIPS machine donated by Broadcom using GCC 4.1. The aim was to find problems in GCC 4.1 itself and bugs in free software projects exhibited by GCC's increased standards conformance (in particular regarding C++ code). Read more for the details.
Order by: Score:
typo in the header
by sequethin on Tue 28th Mar 2006 21:32 UTC
sequethin
Member since:
2005-07-06

pretty sure that should say "Building the Whole Debian...." ;)

Reply Score: 3

RE: typo in the header
by korpenkraxar on Tue 28th Mar 2006 21:47 UTC in reply to "typo in the header"
korpenkraxar Member since:
2005-09-10

nope, it should actually read "the Ghoul Debian" ;-)

Edited 2006-03-28 21:47

Reply Score: 1

Nice
by dikatlon on Tue 28th Mar 2006 22:10 UTC
dikatlon
Member since:
2005-07-08

I like this, it shows how powerful OSS is.
Sometimes you think that, "heey what's up with the devs - are they just creating bells and whistles?"; wooah this is nice indeed.

Edited 2006-03-28 22:10

Reply Score: 1

speedy enhancement
by netpython on Wed 29th Mar 2006 07:29 UTC
netpython
Member since:
2005-07-06

I´m recompiling everything with my own optimalisation flags on Ubuntu too,for fun.At least i get some 64-bit packages of otherwise 32-bit packages.

Reply Score: 1

This is wonderful
by ishmal on Wed 29th Mar 2006 11:37 UTC
ishmal
Member since:
2005-11-11

The more warnings and errors that the compiler can generate, the better. My old CS prof once said, "If you are lucky, it won't compile." Developers should always use -Wall, and pay attention to the results. When you work off the warnings, you will feel a lot better. And you will be surprised how many potential bugs you will find.

Reply Score: 2

RE: This is wonderful
by ameasures on Wed 29th Mar 2006 12:50 UTC in reply to "This is wonderful"
ameasures Member since:
2006-01-09

--Developers should always use -Wall, and pay attention to the results.

Quite so, I use the Wall flag together with the pedantic flags. Clean code is both portable and reusable. It also advances my understanding of the language (together with peer estimations of my skills).

The point about new checks generating warnings rather than errors has some validity though perhaps not every time.

Reply Score: 1

Broadcom?
by Nathan O. on Wed 29th Mar 2006 15:14 UTC
Nathan O.
Member since:
2005-08-11

I thought Broadcom was mostly known for wifi that didn't work in OSS. Neat!

Reply Score: 1

Good Job
by microFawad on Wed 29th Mar 2006 20:43 UTC
microFawad
Member since:
2005-12-09

Mr. Martin had done really a good job. 500 bugs - wow.

Reply Score: 1

Another good flag to use...
by bnolsen on Thu 30th Mar 2006 15:19 UTC
bnolsen
Member since:
2006-01-06

also useful is to add the -Weffc++, which throws out warnings about code which doesn't meet the suggestions made in the "More Effective C++" series.

Reply Score: 1