Skip to content

L
linux
An error occurred fetching the project authors.
Switch branch/tag
  1. 07 Feb, 2016 1 commit
  3. 28 Jan, 2016 1 commit
  5. 11 Jan, 2016 1 commit
  7. 14 Dec, 2015 1 commit
  9. 18 Nov, 2015 1 commit
  11. 30 Oct, 2015 1 commit
  13. 06 Oct, 2015 1 commit
  15. 11 Sep, 2015 1 commit
  17. 20 Aug, 2015 1 commit
  19. 10 Aug, 2015 1 commit
  21. 20 Jul, 2015 1 commit
  23. 30 Jun, 2015 1 commit
  25. 11 Jun, 2015 1 commit
  27. 28 May, 2015 2 commits
    • Kirill A. Shutemov's avatar
      kernel: use the gnu89 standard explicitly · 6e0fc212
      Kirill A. Shutemov authored 
      commit 51b97e35 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: default avatarSasha Levin <sasha.levin@oracle.com>
Singed-off-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
Cc: Philip Müller <philm@manjaro.org>
Signed-off-by: default avatarLuis Henriques <luis.henriques@canonical.com>
      6e0fc212
    • Luis Henriques's avatar
      Linux 3.16.7-ckt12 · 5de41390
      Luis Henriques authored 
      Signed-off-by: default avatarLuis Henriques <luis.henriques@canonical.com>
      5de41390
  29. 12 May, 2015 1 commit
  31. 27 Apr, 2015 1 commit
  33. 30 Mar, 2015 1 commit
  35. 11 Mar, 2015 1 commit
  37. 24 Feb, 2015 1 commit
  39. 10 Feb, 2015 1 commit
  41. 02 Feb, 2015 1 commit
  43. 15 Jan, 2015 1 commit
  45. 19 Dec, 2014 1 commit
  47. 01 Dec, 2014 1 commit
  49. 14 Nov, 2014 1 commit
  51. 30 Oct, 2014 1 commit
  53. 15 Oct, 2014 1 commit
  55. 09 Oct, 2014 1 commit
  57. 05 Oct, 2014 1 commit
  59. 17 Sep, 2014 1 commit
  61. 05 Sep, 2014 1 commit
  63. 14 Aug, 2014 1 commit
  65. 03 Aug, 2014 1 commit
  67. 27 Jul, 2014 1 commit
  69. 26 Jul, 2014 1 commit
    • Linus Torvalds's avatar
      Fix gcc-4.9.0 miscompilation of load_balance() in scheduler · 2062afb4
      Linus Torvalds authored 
      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=61801Reported-by: default avatarMichel Dänzer <michel@daenzer.net>
Suggested-by: default avatarMarkus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jakub Jelinek <jakub@redhat.com>
Cc: stable@kernel.org
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      2062afb4
  71. 21 Jul, 2014 1 commit
  73. 13 Jul, 2014 1 commit
  75. 06 Jul, 2014 1 commit
  77. 04 Jul, 2014 1 commit
    • Michal Marek's avatar
      kbuild: Fix packaging targets with relative $(srctree) · c79624c1
      Michal Marek authored 
      All other users of Makefile.build set $(obj) to the name of the
subdirectory to build. Do the same for the packaging targets, otherwise
the build fails if $(srctree) is a relative directory:

    $ make O=build tar-pkg
    make[1]: Entering directory `/home/mmarek/linux-2.6/build'
      CHK     include/config/kernel.release
    ../scripts/Makefile.build:44: ../../scripts/package/Makefile: No such file or directory
    make[2]: *** No rule to make target `../../scripts/package/Makefile'.  Stop.

Fixes: 9da0763b ("kbuild: Use relative path when building in a subdir of the source tree")
Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      c79624c1
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7