1. 24 6月, 2017 1 次提交
  2. 16 5月, 2017 1 次提交
  3. 14 5月, 2017 1 次提交
  4. 10 5月, 2017 1 次提交
  5. 09 5月, 2017 1 次提交
  6. 03 5月, 2017 1 次提交
  7. 01 5月, 2017 1 次提交
  8. 28 4月, 2017 1 次提交
  9. 25 4月, 2017 1 次提交
  10. 24 4月, 2017 1 次提交
  11. 23 4月, 2017 2 次提交
  12. 18 4月, 2017 1 次提交
    • M
      kbuild: avoid conflict between -ffunction-sections and -pg on gcc-4.7 · 90ad4052
      Masahiro Yamada 提交于
      Arnd Bergmann reported:
        "When ftrace is enabled and we build with gcc-4.7 or older, we
        get a warning for each file on architectures that select
        CONFIG_LD_DEAD_CODE_DATA_ELIMINATION:
      
        warning: -ffunction-sections disabled; it makes profiling impossible [enabled by default]
        "
      
      Since commit c3f0d0bc ("kbuild, LLVMLinux: Add -Werror to
      cc-option to support clang"), warnings are treated as errors in
      cc-option checks.  CC_FLAGS_FTRACE is blindly added to KBUILD_CFLAGS,
      so $(call cc-option,-ffunction-sections,) should be moved below it
      in order to detect the conflict between the two options.
      Reported-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      90ad4052
  13. 17 4月, 2017 1 次提交
  14. 13 4月, 2017 1 次提交
  15. 10 4月, 2017 1 次提交
  16. 03 4月, 2017 1 次提交
  17. 31 3月, 2017 1 次提交
  18. 27 3月, 2017 1 次提交
  19. 22 3月, 2017 2 次提交
  20. 20 3月, 2017 1 次提交
  21. 17 3月, 2017 1 次提交
    • A
      Kbuild: use cc-disable-warning consistently for maybe-uninitialized · b334e19a
      Arnd Bergmann 提交于
      In commit a76bcf55 ("Kbuild: enable -Wmaybe-uninitialized warning
      for "make W=1""), I reverted another change that happened to fix a problem
      with old compilers, and now we get this report again with old compilers
      (prior to gcc-4.8) and GCOV enabled:
      
         cc1: warnings being treated as errors
         drivers/gpu/drm/i915/intel_ringbuffer.c: In function 'intel_ring_setup_status_page':
         drivers/gpu/drm/i915/intel_ringbuffer.c:438: error: 'mmio.reg' may be used uninitialized in this function
         At top level:
      >> cc1: error: unrecognized command line option "-Wno-maybe-uninitialized"
      
      The problem is that we turn off the warning conditionally in a number
      of places as we should, but one of them does it unconditionally.
      Instead, change it to call cc-disable-warning as we do elsewhere.
      
      The original patch that caused it was merged into linux-4.7, then
      4.8 removed the change and 4.9 brought it back, so we probably want
      a backport to 4.9 once this is merged.
      
      Use a ':=' assignment instead of '=' to force the cc-disable-warning
      call to only be evaluated once instead of every time.
      
      Cc: stable@vger.kernel.org
      Fixes: a76bcf55 ("Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"")
      Fixes: e72e2dfe ("gcov: disable -Wmaybe-uninitialized warning")
      Reported-by: Nkbuild test robot <fengguang.wu@intel.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      b334e19a
  22. 15 3月, 2017 1 次提交
  23. 13 3月, 2017 1 次提交
  24. 11 3月, 2017 1 次提交
  25. 06 3月, 2017 1 次提交
  26. 20 2月, 2017 2 次提交
  27. 16 2月, 2017 1 次提交
  28. 13 2月, 2017 1 次提交
  29. 06 2月, 2017 1 次提交
  30. 04 2月, 2017 1 次提交
  31. 30 1月, 2017 1 次提交
  32. 27 1月, 2017 1 次提交
  33. 23 1月, 2017 1 次提交
  34. 16 1月, 2017 1 次提交
  35. 09 1月, 2017 1 次提交
  36. 02 1月, 2017 1 次提交
  37. 26 12月, 2016 1 次提交