Re: Old compiler versions (was Re: v4.10: kernel stack frame pointer .. has bad value (null))

On Thu, Mar 9, 2017 at 2:49 AM, Pavel Machek wrote: > > (On thinkpad X220, compiling bzip2) You really shouldn't assume that the zlib build tracks the kernel build. At least at some point, a noticeable part of the build cost for the kernel was just parsing the fairly big source

Re: Old compiler versions (was Re: v4.10: kernel stack frame pointer .. has bad value (null))

On Thu, Mar 9, 2017 at 2:49 AM, Pavel Machek wrote: > > (On thinkpad X220, compiling bzip2) You really shouldn't assume that the zlib build tracks the kernel build. At least at some point, a noticeable part of the build cost for the kernel was just parsing the fairly big source code. We have

Old compiler versions (was Re: v4.10: kernel stack frame pointer .. has bad value (null))

Hi! > > > - CONFIG_FUNCTION_GRAPH_TRACER sets it on x86-32 because of a gcc bug > > > where the stack gets aligned before the mcount call. This issue > > > should be mostly obsolete as most modern compilers now have -mfentry. > > > We could make it dependent on CC_USING_FENTRY. > > > >

Old compiler versions (was Re: v4.10: kernel stack frame pointer .. has bad value (null))

Hi! > > > - CONFIG_FUNCTION_GRAPH_TRACER sets it on x86-32 because of a gcc bug > > > where the stack gets aligned before the mcount call. This issue > > > should be mostly obsolete as most modern compilers now have -mfentry. > > > We could make it dependent on CC_USING_FENTRY. > > > >