On 02/25/14 17:17, Dave Jones wrote:
On Tue, Feb 25, 2014 at 05:08:40PM -0800, behanw@xxxxxxxxxxxxxxxxxx wrote:
> +warning-1 += $(call cc-disable-warning, self-assign)
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.
Some of the others may also be interesting.
I don't have one now, but I can generate a log and send it to you. We've
had that option set from near the beginning of the porting effort.
This are primarily off due to the amount of noise these warnings produce
at this time (clang produces a LOT of warnings straight out of the box).
I'd love to eventually turn some of these back on again.
Thanks,
Behan
--
Behan Webster
behanw@xxxxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
