All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Michal Marek <mmarek@suse.cz>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: LTO build errors (Re: linux-next: clean up the kbuild tree?)
Date: Mon, 30 Nov 2015 09:46:45 -0800	[thread overview]
Message-ID: <20151130174645.GC3528@tassilo.jf.intel.com> (raw)
In-Reply-To: <s5h7fl6a7lg.wl-tiwai@suse.de>

> > > /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'
> > 
> > 
> > That's new, but can be fixed by adding __visible or asmlinkage to these symbols
> > I guess it's from the recent entry* restructuring.
> > 
> > I'll do an updated tree later.
> > 
> > Everything that's called from assembler in C needs to be marked like this. It's
> > fairly mechanic.
> 
> OK, thanks for the information!

I uploaded lto-4.1/4.2/4.3 trees to my git tree. It only needed some minor changes.

However I think the problems with the assembler labels you had are due to toolchain
misconfiguration. I had the same issue when the compiler was using the non Linux binutils
as plugin ld. Unfortunately there is no way to ask the compiler to use a different
plugin ld, other than:
- rebuilding and specifying it at build time (see "Documentation/lto-build")
- or replacing the linker binary (/usr/bin/ld in a standard hosted compiler)

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

      reply	other threads:[~2015-11-30 17:48 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           ` LTO build errors (Re: linux-next: clean up the kbuild tree?) Takashi Iwai
2015-11-25  4:33             ` Andi Kleen
2015-11-25  6:58               ` Takashi Iwai
2015-11-30 17:46                 ` Andi Kleen [this message]

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=20151130174645.GC3528@tassilo.jf.intel.com \
    --to=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 \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.