On Sun, Feb 20, 2011 at 05:35:10PM +0100, Borislav Petkov wrote: > Add a 'W=1' Makefile switch which adds additional checking per build > object. > > The idea behind this option is targeted at developers who, in the > process of writing their code, want to do the occasional > > make W=1 [target.o] > > and let gcc do more extensive code checking for them. Then, they > could eyeball the output for valid gcc warnings about various > bugs/discrepancies which are not reported during the normal build > process. > > For more background information and a use case, read through this > thread: http://marc.info/?i=20110218091716.GA4384@bicker > > Cc: Ingo Molnar <mingo@xxxxxxx> > Cc: Michal Marek <mmarek@xxxxxxx> > Cc: linux-kbuild@xxxxxxxxxxxxxxx > Signed-off-by: Borislav Petkov <bp@xxxxxxxxx> > --- > Makefile | 31 +++++++++++++++++++++++++++++++ > 1 files changed, 31 insertions(+), 0 deletions(-) I like the idea. But can we avoid polluting the top-level Makefile? That file is full of unreadable stuff, and adding more is not good. Makefile.lib or Makefile.build seems like a better place for this. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
