>
> kallsyms failure: relative symbol value 0x8100 out of
> range in relative mode
>
> I seem to get that all the time here, and have also disabled it for now,
> but it sounds important (and breaks the build).
Need to take a look at it.
I had some patches that completely revamped k
On Sat, Jan 27, 2018 at 1:55 AM, Andi Kleen wrote:
> On Sat, Jan 27, 2018 at 01:15:49AM +0100, Arnd Bergmann wrote:
>> On Mon, Nov 27, 2017 at 10:34 PM, Andi Kleen wrote:
>> > From: Andi Kleen
>> > - Add a new LDFINAL variable that controls the final link
>> > for vmlinux or module. In this case
On Sat, Jan 27, 2018 at 01:15:49AM +0100, Arnd Bergmann wrote:
> On Mon, Nov 27, 2017 at 10:34 PM, Andi Kleen wrote:
> > From: Andi Kleen
> > - Add a new LDFINAL variable that controls the final link
> > for vmlinux or module. In this case we call gcc-ld instead
> > of ld, to run the LTO step.
>
On Mon, Nov 27, 2017 at 10:34 PM, Andi Kleen wrote:
> From: Andi Kleen
> - Add a new LDFINAL variable that controls the final link
> for vmlinux or module. In this case we call gcc-ld instead
> of ld, to run the LTO step.
When I tried this out on allmodconfig (following the lwn article), I ran i
From: Andi Kleen
With LTO gcc will do whole program optimizations for
the whole kernel and each module. This increases compile time,
and makes incremential builds slower, but can generate faster and
smaller code and allows the compiler to do some global checking.
gcc can complain now about type
5 matches
Mail list logo
