lkml.org 
[lkml]   [2020]   [May]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.6 127/194] gcc-10: disable zero-length-bounds warning for now
    Date
    From: Linus Torvalds <torvalds@linux-foundation.org>

    commit 5c45de21a2223fe46cf9488c99a7fbcf01527670 upstream.

    This is a fine warning, but we still have a number of zero-length arrays
    in the kernel that come from the traditional gcc extension. Yes, they
    are getting converted to flexible arrays, but in the meantime the gcc-10
    warning about zero-length bounds is very verbose, and is hiding other
    issues.

    I missed one actual build failure because it was hidden among hundreds
    of lines of warning. Thankfully I caught it on the second go before
    pushing things out, but it convinced me that I really need to disable
    the new warnings for now.

    We'll hopefully be all done with our conversion to flexible arrays in
    the not too distant future, and we can then re-enable this warning.

    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    Makefile | 3 +++
    1 file changed, 3 insertions(+)

    --- a/Makefile
    +++ b/Makefile
    @@ -857,6 +857,9 @@ KBUILD_CFLAGS += -Wno-pointer-sign
    # disable stringop warnings in gcc 8+
    KBUILD_CFLAGS += $(call cc-disable-warning, stringop-truncation)

    +# We'll want to enable this eventually, but it's not going away for 5.7 at least
    +KBUILD_CFLAGS += $(call cc-disable-warning, zero-length-bounds)
    +
    # Enabled with W=2, disabled by default as noisy
    KBUILD_CFLAGS += $(call cc-disable-warning, maybe-uninitialized)


    \
     
     \ /
      Last update: 2020-05-18 20:09    [W:4.107 / U:0.308 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site