From: Nicholas Piggin <npiggin@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Michal Marek <mmarek@suse.com>,
Chen Liqin <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'
Date: Tue, 13 Sep 2016 12:00:14 +1000 [thread overview]
Message-ID: <20160913120014.1036bf91@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20160912222443.GA8425@roeck-us.net>
On Mon, 12 Sep 2016 15:24:43 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> Hi,
>
> your commit 'kbuild: allow archs to select link dead code/data elimination'
> is causing the following build failure in -next when building score:defconfig.
>
> arch/score/kernel/built-in.o: In function `work_resched':
> arch/score/kernel/entry.o:(.text+0xe84):
> relocation truncated to fit: R_SCORE_PC19 against `schedule'
>
> Reverting the commit fixes the problem.
>
> Please let me know if I can help tracking down the problem.
> In case you need a score toochain, you can find the one I use at
> http://server.roeck-us.net/toolchains/score.tgz.
>
> Thanks,
> Guenter
It's not supposed to have any real effect unless the
option is selected, but there are a few changes to linker
script which must be causing it.
There are two changes to vmlinux.lds.h. One is to KEEP a
few input sections, that *should* be kept anyway. The other
is to bring in additional sections into their correct output
section.
Could you try reverting those lines of vmlinux.lds.h that
change the latter, i.e.:
- *(.text.hot .text .text.fixup .text.unlikely) \
+ *(.text.hot .text .text.fixup .text.unlikely .text.*) \
- *(.bss) \
+ *(.bss .bss.[0-9a-zA-Z_]*) \
etc?
Thanks,
Nick
next prev parent reply other threads:[~2016-09-13 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:24 Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination' Guenter Roeck
2016-09-13 2:00 ` Nicholas Piggin [this message]
2016-09-13 3:17 ` Guenter Roeck
2016-09-13 3:51 ` Nicholas Piggin
2016-09-13 20:25 ` Guenter Roeck
2016-09-14 2:30 ` Nicholas Piggin
2016-09-14 19:48 ` Guenter Roeck
2016-09-22 12:38 ` Michal Marek
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=20160913120014.1036bf91@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=mmarek@suse.com \
/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).