From: Guenter Roeck <linux@roeck-us.net>
To: Nicholas Piggin <npiggin@gmail.com>
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 13:25:22 -0700 [thread overview]
Message-ID: <f4bff2ed-26b4-29b7-e51a-ac5e5ece58a2@roeck-us.net> (raw)
In-Reply-To: <20160913135115.089a933b@roar.ozlabs.ibm.com>
On 09/12/2016 08:51 PM, Nicholas Piggin wrote:
> On Mon, 12 Sep 2016 20:17:30 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
>
>> Hi Nicholas,
>>
>> On 09/12/2016 07:00 PM, Nicholas Piggin wrote:
>>> 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.*) \
>>
>> This is the culprit. After removing " .text.*" it builds fine.
>
> Thanks for testing it. Some architectures have .text.x sections
> not included here, I should have seen that. We should possibly
> just revert that line and require implementing archs to do the
> right thing.
>
I would call the build failure a regression, so it should either be
reverted, or we'll need some other solution to fix the build failure.
Thanks,
Guenter
> [ Convention is to use '.' to avoid C identifiers, so we should
> use .text..x for these things. But that's not done completely
> throughout the kernel, and a little invasive to do with this
> series. I'll revisit this and clean things up subsequently after
> this round gets merged. ]
>
> Thanks,
> Nick
>
next prev parent reply other threads:[~2016-09-13 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 22:24 Guenter Roeck
2016-09-13 2:00 ` Nicholas Piggin
2016-09-13 3:17 ` Guenter Roeck
2016-09-13 3:51 ` Nicholas Piggin
2016-09-13 20:25 ` Guenter Roeck [this message]
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=f4bff2ed-26b4-29b7-e51a-ac5e5ece58a2@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.linux@gmail.com \
--cc=mmarek@suse.com \
--cc=npiggin@gmail.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
all inboxes | Powered by JetHome®