Re: RFC: How to handle function tracing, frame pointers and -mfentry?

["H. Peter Anvin" <hpa@xxxxxxxxx>]

On 04/28/2012 01:36 AM, Andi Kleen wrote:
> 
> Kconfig just needs to learn how to run the target compiler
> 
> I think that's the right direction. Right now our main
> Makefiles get polluted more and more with "test compiles", each
> of which makes a "null make" slower and slower. 
> 
> I just measured and a null compile (nothing changes) of a current
> tree calls "gcc" 141 times.
> 
> All this stuff should be cached in the Kconfig instead.
> 
> It may break some obscure setups (that can be probably fixed without
> too much effort), but the development turnaround improvement
> for everyone else would be worth it.
> 

I don't think it is a performance issue as much as a utility issue.
When Kconfig can't actually reflect what is built into the resulting
kernel, that is a problem.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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