linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: link error on orphan sections
Date: Fri, 14 Oct 2016 16:37:45 +1100	[thread overview]
Message-ID: <20161014163745.11bcb772@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <14286beb-d100-5877-7725-37402d7ac38d@gmail.com>

On Fri, 14 Oct 2016 13:35:54 +1100
Balbir Singh <bsingharora@gmail.com> wrote:

> On 12/10/16 18:00, Nicholas Piggin wrote:
> > Add --orphan-handling=error to final link flags. This ensures we have to
> > handle all sections. This would have caught subtle breakage such as
> > 7de3b27bac47da9de08409df1d69664acbb72197 at build-time.
> > 
> > Also bring some wayward sections into the fold:
> > - .text.hot and .text.unlikely are compiler generated sections.
> > - .sfpr is a linker generated section for register save functions.
> > - .sdata2, .dynsbss, .plt are used by PPC32
> > - We previously did not specify DWARF_DEBUG or STABS_DEBUG
> > - DWARF_DEBUG did not include DWARF3 .debug_ranges
> > - A number of sections are unused.
> > 
> > I don't know if I've exactly got everything right here, particularly
> > with ppc32, so would appreciate people casting their eye over it.
> > 
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> >  arch/powerpc/Makefile             |  2 +-
> >  arch/powerpc/kernel/vmlinux.lds.S | 16 ++++++++++++++--
> >  include/asm-generic/vmlinux.lds.h |  3 +++
> >  3 files changed, 18 insertions(+), 3 deletions(-)
> > 
> > diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> > index 50d020a..a3f2784 100644
> > --- a/arch/powerpc/Makefile
> > +++ b/arch/powerpc/Makefile
> > @@ -90,7 +90,7 @@ endif
> >  
> >  LDFLAGS_vmlinux-y := -Bstatic
> >  LDFLAGS_vmlinux-$(CONFIG_RELOCATABLE) := -pie
> > -LDFLAGS_vmlinux	:= $(LDFLAGS_vmlinux-y)
> > +LDFLAGS_vmlinux	:= $(LDFLAGS_vmlinux-y) --orphan-handling=error
> >  
> >  ifeq ($(CONFIG_PPC64),y)
> >  ifeq ($(call cc-option-yn,-mcmodel=medium),y)
> > diff --git a/arch/powerpc/kernel/vmlinux.lds.S b/arch/powerpc/kernel/vmlinux.lds.S
> > index 8295f51..9f4d85e 100644
> > --- a/arch/powerpc/kernel/vmlinux.lds.S
> > +++ b/arch/powerpc/kernel/vmlinux.lds.S
> > @@ -97,7 +97,7 @@ SECTIONS
> >  	.text : AT(ADDR(.text) - LOAD_OFFSET) {
> >  		ALIGN_FUNCTION();
> >  		/* careful! __ftr_alt_* sections need to be close to .text */
> > -		*(.text .fixup __ftr_alt_* .ref.text)
> > +		*(.text.hot .text .text.fixup .text.unlikely .fixup __ftr_alt_* .ref.text .sfpr) \
> >  		SCHED_TEXT  
> 
> Is the "\" to pack the sched_text with the rest of .text?

Actually it looks like a typo that slipped in. Good catch.


> > @@ -256,7 +256,9 @@ SECTIONS
> >  	.data : AT(ADDR(.data) - LOAD_OFFSET) {
> >  		DATA_DATA
> >  		*(.sdata)
> > +		*(.sdata2)
> >  		*(.got.plt) *(.got)
> > +		*(.plt)
> >  	}
> >  #else
> >  	.data : AT(ADDR(.data) - LOAD_OFFSET) {
> > @@ -317,6 +319,16 @@ SECTIONS
> >  	_end = . ;
> >  	PROVIDE32 (end = .);
> >  
> > -	/* Sections to be discarded. */
> > +	STABS_DEBUG
> > +
> > +	DWARF_DEBUG
> > +  
> 
> Are the debug sections discarded or is the above
> comment misplaced? I guess they are discarded because of them
> being outside of _end at relocation.

I just got rid of the comment. Having it right above "DISCARDS" seemed
redundant.

I believe the debug sections will be linked into the file, because they
were not put in the /DISCARD/ output. But they will be outside the _end
symbol.

Thanks,
Nick

  reply	other threads:[~2016-10-14  5:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  7:00 [PATCH] powerpc: link error on orphan sections Nicholas Piggin
2016-10-14  0:46 ` Michael Ellerman
2016-10-14 10:54   ` David Laight
2016-10-19 11:56     ` Michael Ellerman
2016-10-19 12:36       ` David Laight
2016-10-14  2:35 ` Balbir Singh
2016-10-14  5:37   ` Nicholas Piggin [this message]
2016-10-14  3:27 ` Michael Ellerman
2016-10-14  5:24   ` 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=20161014163745.11bcb772@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).