4 ms·
>Raising the minimum GCC version to 8.x would likely be more of a jump than the user community would be willing to accept at this point. If you are using a 0 d
by charcircuit 5y ago
>Raising the minimum GCC version to 8.x would likely be more of a jump than the user community would be willing to accept at this point.
If you are using a 0 day old kernel. Why would you be using GCC 5.x still. 5
1 is almost 7 years old now. 8.1 is almost 4. Can't people just use apt / yum / rpm / whatever to upgrade to the latest gcc? Is that really too much to ask of the community?
- lazide 5y agoFor an unstable branch maybe, but if people need to actually use this for real work they will want it compiling on something as well understood and baked as possible - while not being completely obsolete.
- charcircuit 5y agoPeople doing real work are using a kernel compiled with a more up to date GCC. From what I can tell online even RHEL is up to date enough by compiling its kernel with GCC 8.x.
- jahlove 5y agoRHEL7 is still supported [0] by Red Hat through 2026, and is on GCC 4.8.5 [1] [0] https://access.redhat.com/product-life-cycles/?product=Red%20Hat%20Enterprise%20Linux,OpenShift%20Container%20Platform%204 https://access.redhat.com/product-life-cycles/?product=Red%2... [1] https://distrowatch.com/table.php?distribution=redhat https://distrowatch.com/table.php?distribution=redhat
- charcircuit 5y agoCorrect me if I'm wrong but doesn't RHEL stick to a single kernel version and then backport patches?
- yjftsjthsd-h 5y agoOfficially yes, although we can argue about how much you can "backport" and still count. But even so - if new code requires a newer C version and thus newer compiler, it's harder to backport.
- mwcremer 5y agoIt's not just a question of what the new version fixes, there is also the question of what it breaks. Sometimes new versions trigger latent bugs no one knew about that luckily happened to work fine on the old tools. Finding and fixing those can be difficult and time-consuming.
- charcircuit 5y agoThis argument would have merit if everyone still used 5.x to compile Linux, but that's simply not the truth. Most people are using a Linux compiled by a somewhat up to date version of GCC.
- bombcar 5y agoThe Linux community is way way way larger than just the sum of distro user bases. Even if all distros have long ago moved to GCC 8+, you still have other chips and systems running, and who knows what buried somewhere depends on GCC 5.
- charcircuit 5y agoYou can compile Linux and a user space program with different versions of GCC.
- Koshkin 5y agoAs well as with Tiny C (fast).
- spicybright 5y agoYou'll have to upgrade the compiler eventually though, right? I don't know what that process would look like, but generally the longer you wait the more pain you'll face later.
- lazide 5y agoNope, it’s open source and some companies will keep it around until they fold in however many years (100?) If it works, why spent money ‘fixing’ it after all.
- spicybright 5y agoCompiler tech and hardware will improve drastically in the next 100 years. Linux can either evolve with it, or be put in a museum while something else takes it's place. Likely losing a lot of the development that's been done in the past 30 years. It would be like running OS/8 (for the PDP-8, popular in 1965) on a modern machine. No time sharing for processes, no network stack, only a TTY for I/O... what would you even do with it if you could compile it?
- 5y ago
- syncsynchalt 5y agoYou'd be surprised how much downstream grief a bump like this can cause in an ecosystem as broad as the Linux kernel. Dealing with the results can be unexpectedly overwhelming. It makes sense to play it safe and do this in smaller incremental jumps.
- pm215 5y agoI get the impression that a big part of it is just a general choice to be very conservative about forcing newer minimum versions. So to raise the version bar you have to make the positive case for why it's worthwhile -- merely "gcc 5 is ancient" doesn't suffice. The only reason it moved up from 4.9 is actual data-loss-provoking codegen bugs in 4.9 (see discussion in this lkml thread: https://lore.kernel.org/lkml/CAHk-=wjqGRXUp6KOdx-eHYEotGvY=a5tSY1mF-BkAcX2YAuBYw@mail.gmail.com/ https://lore.kernel.org/lkml/CAHk-=wjqGRXUp6KOdx-eHYEotGvY=a... )... I do think they could move up a bit further, but it's useful to be able to just build kernels with the distro compiler and repology thinks that for instance Debian stretch (still an LTS supported version) is only gcc 6.3.
- charcircuit 5y agoDebian stretch uses the 4.19 LTS branch. A switch to a new GCC would happen in a new version.
- pm215 5y agoThe distro kernel will stay on the LTS branch, certainly -- but the upstream kernel folk like people to be able to compile upstream kernels and not have to stick with the distro ones. (I've done it myself on occasion and i'm not a kernel dev; if I'd had to also get hold of a new gcc it would have been an irritating extra step.)
- mhh__ 5y agoPeople love making a fuss about this kind of thing. It's totally meaningless and usually dominated by the fact they've been asked to migrate, but it's still true unfortunately.