3 ms·
> In comparison, it sounds like gcc and the linux kernel devs are mutually confused about whether 4.9 is supported software. There is no such confusion. Nobody
by detaro 6y ago
> In comparison, it sounds like gcc and the linux kernel devs are mutually confused about whether 4.9 is supported software.
There is no such confusion. Nobody expects GCC to maintain a 4.9 release line (but other entities do maintain such lines through backporting). Kernel developers had decided they are not going to intentionally break support for builds with GCC 4.9 unless they have a reason to.
- josephg 6y agoRight; but this is my point. Either we expect GCC 4.9 to produce correct code, or we don't. "Mostly correct" is poison, and should be avoided whenever possible. If we expect GCC 4.9 to produce correct code then patches should be backported to GCC 4.9. (I mean, we expect it to produce correct code, right??) If we don't expect GCC 4.9 to produce correct code, why are some mainline distributions compiling their kernel with GCC 4.9? Why is the linux kernel accepting bug reports from people who have compiled the kernel with a known buggy version of GCC? The article made the same point - the problem here is that people are running into a GCC bug that was fixed years ago. The two solutions are to either backport GCC bug fixes to gcc 4.9 consistently, or stop depending on gcc 4.9. The kernel devs + gcc authors should pick one. The ambiguity wastes everyone's time.