From: Nicholas Piggin <npiggin@gmail.com>
To: Mathieu Malaterre <malat@debian.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: 83a092cf95f28: powerpc: Link warning for orphan sections
Date: Tue, 3 Jul 2018 17:23:32 +1000 [thread overview]
Message-ID: <20180703172332.7210ec7a@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <CA+7wUsz6AWY63hCwax2YSUPawRQbLfyje23qWKNGVUGM=OxM4Q@mail.gmail.com>
On Tue, 3 Jul 2018 09:03:46 +0200
Mathieu Malaterre <malat@debian.org> wrote:
> Hi Nick,
>
> I am building my kernel (ppc32) with both
> CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y and CONFIG_UBSAN=y. This leads
> to ~316428 warnings such as:
>
> + powerpc-linux-gnu-ld -EB -m elf32ppc -Bstatic --orphan-handling=warn
> --build-id --gc-sections -X -o .tmp_vmlinux1 -T
> ./arch/powerpc/kernel/vmlinux.lds --who
> le-archive built-in.a --no-whole-archive --start-group lib/lib.a --end-group
> powerpc-linux-gnu-ld: warning: orphan section `.data..Lubsan_data393'
> from `init/main.o' being placed in section `.data..Lubsan_data393'.
> powerpc-linux-gnu-ld: warning: orphan section `.data..Lubsan_data394'
> from `init/main.o' being placed in section `.data..Lubsan_data394'.
> powerpc-linux-gnu-ld: warning: orphan section `.data..Lubsan_data395'
> from `init/main.o' being placed in section `.data..Lubsan_data395'.
> powerpc-linux-gnu-ld: warning: orphan section `.data..Lubsan_data396'
> from `init/main.o' being placed in section `.data..Lubsan_data396'.
> ...
>
> What would you recommend to reduce the number of warnings produced ? I
> tried `--warn-once` but that only affect undefined symbols.
I'm not sure if the linker can be quietened. You could try putting
*(.data..Lubsan_data*) into the .data section in
powerpc/kernel/vmlinux.lds.S
Thanks,
Nick
next prev parent reply other threads:[~2018-07-03 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 7:03 83a092cf95f28: powerpc: Link warning for orphan sections Mathieu Malaterre
2018-07-03 7:23 ` Nicholas Piggin [this message]
2018-07-03 7:37 ` Mathieu Malaterre
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=20180703172332.7210ec7a@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.org \
/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