Messages in this thread | | | Date | Tue, 25 Feb 2014 18:38:51 -0800 | From | Behan Webster <> | Subject | Re: [PATCH 2/5] kbuild: LLVMLinux: Adapt warnings for compilation with clang |
| |
On 02/25/14 17:17, Dave Jones wrote: > On Tue, Feb 25, 2014 at 05:08:40PM -0800, behanw@converseincode.com wrote: > > > When compiling kernel with clang, disable warnings which are too noisy, and > > add the clang flag catch-undefined-behavior. > > > > +# Clang > > +warning-1 += $(call cc-disable-warning, initializer-overrides) > > +warning-1 += $(call cc-disable-warning, unused-value) > > +warning-1 += $(call cc-disable-warning, format) > > +warning-1 += $(call cc-disable-warning, unknown-warning-option) > > +warning-1 += $(call cc-disable-warning, self-assign) > > +warning-1 += $(call cc-disable-warning, sign-compare) > > +warning-1 += $(call cc-disable-warning, format-zero-length) > > +warning-1 += $(call cc-disable-warning, uninitialized) > > +warning-1 += $(call cc-option, -fcatch-undefined-behavior) > > Do you have a pointer to an example log-file from before this change ? > I'm curious for eg, which self-assign warnings are showing up, > because I've been fixing up the ones that Coverity found, of which > there are only a dozen or so left iirc. I count 22 in this particular x86 kernel build (some of which you may well have fixed already). Enjoy.
http://buildbot.llvm.linuxfoundation.org/self-assign-build.log.txt
Perhaps I should re-enable that warning, considering the number has dropped so dramatically from when I last checked over a year ago.
Thanks,
Behan
-- Behan Webster behanw@converseincode.com
| |