linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: Michal Marek <mmarek@suse.cz>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: LTO build errors (Re: linux-next: clean up the kbuild tree?)
Date: Tue, 24 Nov 2015 17:33:36 +0100	[thread overview]
Message-ID: <s5hy4dnicgv.wl-tiwai@suse.de> (raw)
In-Reply-To: <20151124021231.GE8438@tassilo.jf.intel.com>

On Tue, 24 Nov 2015 03:12:31 +0100,
Andi Kleen wrote:
> 
> > > 5.x is better than 4.x but it's still a slower. It's also not incremential.
> > 
> > At the last time I tested with the latest 5.x and stock binutils on
> > openSUSE Tumbleweed, I failed to build, unfortunately.  Partly the
> > detection of gcc version doesn't work for 5.x, and partly something is
> 
> Really? It work for me with gcc 5

I retested now, and it seems like only the binutils, not about gcc
version, indeed.  Sorry for confusion.

> > missing in binutils side, although it's already built with plugin.
> 
> Yes it needs HJ Lu's Linux binutils, not the standard FSF binutils.
> The patch to fix LTO with ld -r was submitted to standard binutils, but they
> didn't want to fix the issue.

I did "make allnoconfig", disabled tracers, gcov, etc, and then
enabled LTO.  With hlj version, the build reaches to the almost end
hitting this:

  LD      vmlinux
arch/x86/kernel/cpu/perf_event_intel_rapl.c:66:20: error: rapl_domain_names causes a section type conflict with __setup_str_set_reset_devices
 static const char *rapl_domain_names[NR_RAPL_DOMAINS] __initconst = {
                    ^
init/main.c:159:19: note: ‘__setup_str_set_reset_devices’ was declared here
 __setup("reset_devices", set_reset_devices);

Hmm...  I see no direct relation, but OK, let's try to get rid of
__initconst.  Now it hits lots of other errors like:

`__sw_hweight32' referenced in section `.text' of /tmp/ccUCMU7n.ltrans13.ltrans.o: defined in discarded section `.text' of lib/built-in.o (symbol from plugin)
`__sw_hweight32' referenced in section `.text' of /tmp/ccUCMU7n.ltrans13.ltrans.o: defined in discarded section `.text' of lib/built-in.o (symbol from plugin)
`__sw_hweight32' referenced in section `.text' of /tmp/ccUCMU7n.ltrans13.ltrans.o: defined in discarded section `.text' of lib/built-in.o (symbol from plugin)
`__sw_hweight32' referenced in section `.text' of /tmp/ccUCMU7n.ltrans13.ltrans.o: defined in discarded section `.text' of lib/built-in.o (symbol from plugin)
/tmp/ccUCMU7n.ltrans21.ltrans.o: In function `do_exit':
<artificial>:(.text+0xfc0): undefined reference to `sys_futex'
/tmp/ccUCMU7n.ltrans22.ltrans.o: In function `_do_fork':
<artificial>:(.text+0x39f7): undefined reference to `ret_from_fork'
<artificial>:(.text+0x4428): undefined reference to `ret_from_kernel_thread'
....


Any hints to solve these?


thanks,

Takashi

  reply	other threads:[~2015-11-24 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15  0:27 linux-next: clean up the kbuild tree? Stephen Rothwell
2015-11-15 17:58 ` Andi Kleen
2015-11-16 13:01   ` Michal Marek
2015-11-21  1:00     ` Andi Kleen
2015-11-21 10:55       ` Takashi Iwai
2015-11-24  2:12         ` Andi Kleen
2015-11-24 16:33           ` Takashi Iwai [this message]
2015-11-25  4:33             ` LTO build errors (Re: linux-next: clean up the kbuild tree?) Andi Kleen
2015-11-25  6:58               ` Takashi Iwai
2015-11-30 17:46                 ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hy4dnicgv.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=ak@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).