Re: TRACE_BRANCH_PROFILING breaks gcc warnings

[Steven Rostedt]

On Wed, 2009-04-15 at 00:28 +0200, Johannes Berg wrote:
> With TRACE_BRANCH_PROFILING enabled you get "dummy may be used
> uninitialised" with code like the following (and gcc 4.3.3):
> 
> void *dummy, *c;
> 
> if (a && (dummy = b()))
> 	c = dummy;
> 
> Therefore, allyesconfig has become useless for looking at warnings.
> 
> :(


This has been mentioned before, and I've asked about sending a patch
that would prevent TRACE_BRANCH_PROFILING from being selected with an
allyesconfig.

It is easy to do. I could make it a selection and not a boolean and it
will not select it as default, even for allyes/modconfig

Thoughts?

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/