Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled

To: Harry Pantazis <luserx0%gmail.com@localhost>
Subject: Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled
From: Robert Elz <kre%munnari.OZ.AU@localhost>
Date: Thu, 31 May 2018 08:22:04 +0700

    Date:        Wed, 30 May 2018 19:11:19 +0800
    From:        Harry Pantazis <luserx0%gmail.com@localhost>
    Message-ID:  <CAFXTyT8Pc-SoDWHUSr6yNS8c9AAG59+wesgYaErbWWYPQYtx+g%mail.gmail.com@localhost>

  | Not a big deal, I'm writing a patch to overcome this issue and
  | continuing the error-checking.
  | All are encouraged to submit patches for a fix.

The constants are overflowing int (into the sign bit) - they just need to be 
made unsigned  4U << 29 (etc).

kre

References:
- Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled
  - From: Harry Pantazis
- GENERIC Kernel Build errors with -fsanitize=undefined option enabled
  - From: Harry Pantazis
- Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled
  - From: Kamil Rytarowski

Prev by Date: Re: i2c and indirect vs. direct config
Next by Date: Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled
Previous by Thread: re: ./build.sh -k feature request (was Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled)
Next by Thread: specificdata(9) has no man page
Indexes:

Home | Main Index | Thread Index | Old Index