RFC: Raise required gcc version to 3.2 ?
What is the oldest gcc we want to support in kernel 2.6?
Currently, it's 2.95 .
I'd suggest raising this to 3.2 which should AFAIK not be a problem for any distribution supporting kernel 2.6 .
Is there any good reason why we should not drop support for older compilers?
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 2 lines · Adrian Bunk
Is there any good reason why we should not drop support for older compilers?
Compilation speed? Don't know, using 3 (4?) years old Athlon 2000 it's not a problem unless I need full build 30 times a day.
But people on 266 MHz ARM5 may notice.
Signature · 1 line
Krzysztof Halasa
Quoted 4 lines · Krzysztof Halasa
Compilation speed? Don't know, using 3 (4?) years old Athlon 2000 it's not a problem unless I need full build 30 times a day.
But people on 266 MHz ARM5 may notice.
Hmm, an a 400Mhz PXA 255 I found using gcc 3.x meant I could use xscale rather than older optimizations, and the resulting kernel certainly felt much faster (I never did actually meassure if it was faster or not). Using gcc 2.95 requried changing the cpu optimization lines in the kernel. Of course this was in a kernel patched with the pxa arm patches so it isn't quite the same as the mainline kernel. I certainly won't consider using gcc 2.95 on an arm anymore (although perhaps on older arm models it does make sense).
I have no idea if it took longer to compile with gcc 3.x, but the result seemed better to me. To me performance of the resulting kernel is more important than performance compiling the kernel.
Of course if you leave the choice as 2.95 and above rather than 3.2 and above, people can pick whatever they want based on their needs.
Len Sorensen
Quoted 6 lines · Adrian Bunk
What is the oldest gcc we want to support in kernel 2.6?
Currently, it's 2.95 .
I'd suggest raising this to 3.2 which should AFAIK not be a problem for any distribution supporting kernel 2.6 .
You have all my support for this. Some weird macros and code could be removed from the tree. F.e. One could use [] instead of [0] and there is a baaad macro in include/linux/mmzone.h in need of some healing touches.
Quoted 2 lines
Is there any good reason why we should not drop support for older compilers?
Probably but we should drop support anyways.