From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/4] Try orphan section warning again
Date: Tue, 29 Nov 2016 15:39:38 +1100 [thread overview]
Message-ID: <20161129043942.13848-1-npiggin@gmail.com> (raw)
Hi,
The orphan section warning patch had a minor issue with unhandled
.text.save.restore last time I sent it. I went back and tidied up
crtsavres a bit, so after these, I think we can enable orphan section
warnings.
There is a further step we can take which is to enable
--save-restore-funcs for module link, which means 64-bit does not
need crtsavres at all. That option is only in binutils 2.25 though,
so I'll send that later.
Thanks,
Nick
Nicholas Piggin (4):
powerpc/64: place sfpr section explicitly with the linker script
powerpc/64: do not link crtsavres routines into vmlinux
powerpc/64: do not create new section for save/restore functions
powerpc: link warning for orphan sections
arch/powerpc/Makefile | 1 +
arch/powerpc/kernel/vmlinux.lds.S | 24 ++++++++++++++++++++++--
arch/powerpc/lib/Makefile | 8 ++++++--
arch/powerpc/lib/crtsavres.S | 6 ++----
include/asm-generic/vmlinux.lds.h | 11 +++++++++++
5 files changed, 42 insertions(+), 8 deletions(-)
--
2.10.2
next reply other threads:[~2016-11-29 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 4:39 Nicholas Piggin [this message]
2016-11-29 4:39 ` [PATCH 1/4] powerpc/64: place sfpr section explicitly with the linker script Nicholas Piggin
2016-11-29 4:39 ` [PATCH 2/4] powerpc/64: do not link crtsavres routines into vmlinux Nicholas Piggin
2016-11-29 4:39 ` [PATCH 3/4] powerpc/64: do not create new section for save/restore functions Nicholas Piggin
2016-11-29 4:39 ` [PATCH 4/4] powerpc: link warning for orphan sections Nicholas Piggin
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=20161129043942.13848-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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 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.