That doesnt make any sense tho. The I5 sandybridge is faster clock for clock than my chip so even at a lower clock it should still be awesome. Really hours? I cant believe hours... Maybe half an hour at like 1GHz with only one core enabled. There's just no way it takes hours to compile a kernel on a modern chip like yours.
It's the entire reason the -O0 (no optimization) level even exists. Because time is more important to a developer than the resulting binary speed when you are debugging issues. I'd agree it's a virtual non-issue for release mode code, though.
Guys, don't talk about compile time not being important unless you're a developer and what you're working on is a multi-GB sized project (yes, binary executables, libraries and such, and no data/source code). I've spent one day just recompiling a tiny portion of a project for internal release and usage. About 40 MB (in release) in 8 different versions. Now imagine compiling something about 100 times larger than that, and luckily only in two versions. Obviously, a large portion of this is rarely rebuilt at all, but just copied from central storage, and you only rebuild as small portion of the software as possible, but still, there's a reason for having nightly builds and such. It saves a huge amount of time for developers.
... so yeah, compile time matters a lot.
Oh, and I have a quadcore email@example.comGHz. Stuff can be compiled fast, but still not at all fast enough.
Do you seriously stare at your screen while the compiler is doing work?
Or can't you write makefiles so that you have to rebuild everything every time you touch a file?
Compiling is background work for me. I NEVER wait for compilation to finish. I do actual WORK while waiting.
Every build system I have built or used will not rebuild stuff that does not need rebuilding.
Even extremely large code projects will usually take a minute or so to generate new binary images if I want to try something out.
Clean compilations I usually do overnight, lunch, breaks etc.
GCC's compilation speed is not a problem.
I'd still give an arm and an leg for something that is 10% faster on average, even if it's 10 times slower.
Don't believe me? Ask anyone who is building or using anything that is computational intensive.