summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)Author
2015-06-29Linux 3.10.82v3.10.82Greg Kroah-Hartman
2015-06-22Linux 3.10.81v3.10.81Greg Kroah-Hartman
2015-06-05Linux 3.10.80v3.10.80Greg Kroah-Hartman
2015-06-05kernel: use the gnu89 standard explicitlyKirill A. Shutemov
commit 51b97e354ba9fce1890cf38ecc754aa49677fc89 upstream. Sasha Levin reports: "gcc5 changes the default standard to c11, which makes kernel build unhappy Explicitly define the kernel standard to be gnu89 which should keep everything working exactly like it was before gcc5" There are multiple small issues with the new default, but the biggest issue seems to be that the old - and very useful - GNU extension to allow a cast in front of an initializer has gone away. Patch updated by Kirill: "I'm pretty sure all gcc versions you can build kernel with supports -std=gnu89. cc-option is redunrant. We also need to adjust HOSTCFLAGS otherwise allmodconfig fails for me" Note by Andrew Pinski: "Yes it was reported and both problems relating to this extension has been added to gnu99 and gnu11. Though there are other issues with the kernel dealing with extern inline have different semantics between gnu89 and gnu99/11" End result: we may be able to move up to a newer stdc model eventually, but right now the newer models have some annoying deficiencies, so the traditional "gnu89" model ends up being the preferred one. Signed-off-by: Sasha Levin <sasha.levin@oracle.com> Singed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-05-17Linux 3.10.79v3.10.79Greg Kroah-Hartman
2015-05-13Linux 3.10.78v3.10.78Greg Kroah-Hartman
2015-05-06Linux 3.10.77v3.10.77Greg Kroah-Hartman
2015-04-29Linux 3.10.76v3.10.76Greg Kroah-Hartman
2015-04-19Linux 3.10.75v3.10.75Greg Kroah-Hartman
2015-04-13Linux 3.10.74v3.10.74Greg Kroah-Hartman
2015-03-26Linux 3.10.73v3.10.73Greg Kroah-Hartman
2015-03-18Linux 3.10.72v3.10.72Greg Kroah-Hartman
2015-03-06Linux 3.10.71v3.10.71Greg Kroah-Hartman
2015-02-26Linux 3.10.70v3.10.70Greg Kroah-Hartman
2015-02-11Linux 3.10.69v3.10.69Greg Kroah-Hartman
2015-02-06Linux 3.10.68v3.10.68Greg Kroah-Hartman
2015-01-29Linux 3.10.67v3.10.67Greg Kroah-Hartman
2015-01-27Linux 3.10.66v3.10.66Greg Kroah-Hartman
2015-01-16Linux 3.10.65v3.10.65Greg Kroah-Hartman
2015-01-08Linux 3.10.64v3.10.64Greg Kroah-Hartman
2014-12-16Linux 3.10.63v3.10.63Greg Kroah-Hartman
2014-12-06Linux 3.10.62v3.10.62Greg Kroah-Hartman
2014-11-21Linux 3.10.61v3.10.61Greg Kroah-Hartman
2014-11-14Linux 3.10.60v3.10.60Greg Kroah-Hartman
2014-10-30Linux 3.10.59v3.10.59Greg Kroah-Hartman
2014-10-15Linux 3.10.58v3.10.58Greg Kroah-Hartman
2014-10-09Linux 3.10.57v3.10.57Greg Kroah-Hartman
2014-10-05Linux 3.10.56v3.10.56Greg Kroah-Hartman
2014-09-17Linux 3.10.55v3.10.55Greg Kroah-Hartman
2014-09-05Linux 3.10.54v3.10.54Greg Kroah-Hartman
2014-08-14Linux 3.10.53v3.10.53Greg Kroah-Hartman
2014-08-07Linux 3.10.52v3.10.52Greg Kroah-Hartman
2014-07-31Linux 3.10.51v3.10.51Greg Kroah-Hartman
2014-07-31Fix gcc-4.9.0 miscompilation of load_balance() in schedulerLinus Torvalds
commit 2062afb4f804afef61cbe62a30cac9a46e58e067 upstream. Michel Dänzer and a couple of other people reported inexplicable random oopses in the scheduler, and the cause turns out to be gcc mis-compiling the load_balance() function when debugging is enabled. The gcc bug apparently goes back to gcc-4.5, but slight optimization changes means that it now showed up as a problem in 4.9.0 and 4.9.1. The instruction scheduling problem causes gcc to schedule a spill operation to before the stack frame has been created, which in turn can corrupt the spilled value if an interrupt comes in. There may be other effects of this bug too, but that's the code generation problem seen in Michel's case. This is fixed in current gcc HEAD, but the workaround as suggested by Markus Trippelsdorf is pretty simple: use -fno-var-tracking-assignments when compiling the kernel, which disables the gcc code that causes the problem. This can result in slightly worse debug information for variable accesses, but that is infinitely preferable to actual code generation problems. Doing this unconditionally (not just for CONFIG_DEBUG_INFO) also allows non-debug builds to verify that the debug build would be identical: we can do export GCC_COMPARE_DEBUG=1 to make gcc internally verify that the result of the build is independent of the "-g" flag (it will make the compiler build everything twice, toggling the debug flag, and compare the results). Without the "-fno-var-tracking-assignments" option, the build would fail (even with 4.8.3 that didn't show the actual stack frame bug) with a gcc compare failure. See also gcc bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61801 Reported-by: Michel Dänzer <michel@daenzer.net> Suggested-by: Markus Trippelsdorf <markus@trippelsdorf.de> Cc: Jakub Jelinek <jakub@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-07-28Linux 3.10.50v3.10.50Greg Kroah-Hartman
2014-07-17Linux 3.10.49v3.10.49Greg Kroah-Hartman
2014-07-09Linux 3.10.48v3.10.48Greg Kroah-Hartman
2014-07-06Linux 3.10.47v3.10.47Greg Kroah-Hartman
2014-06-30Linux 3.10.46v3.10.46Greg Kroah-Hartman
2014-06-26Linux 3.10.45v3.10.45Greg Kroah-Hartman
2014-06-16Linux 3.10.44v3.10.44Greg Kroah-Hartman
2014-06-11Linux 3.10.43v3.10.43Greg Kroah-Hartman
2014-06-07Linux 3.10.42v3.10.42Greg Kroah-Hartman
2014-05-31Linux 3.10.41v3.10.41Greg Kroah-Hartman
2014-05-13Linux 3.10.40v3.10.40Greg Kroah-Hartman
2014-05-06Linux 3.10.39v3.10.39Greg Kroah-Hartman
2014-04-26Linux 3.10.38v3.10.38Greg Kroah-Hartman
2014-04-14Linux 3.10.37v3.10.37Greg Kroah-Hartman
2014-04-03Linux 3.10.36v3.10.36Greg Kroah-Hartman
2014-03-31Linux 3.10.35v3.10.35Greg Kroah-Hartman
generated by cgit v1.2.3 (git 2.0.4) at 2024-05-26 01:11:32 +0000