From: Sam Ravnborg <sam@ravnborg.org>
To: Kyle McMartin <kyle@infradead.org>
Cc: linuxppc-dev@ozlabs.org, aoliva@redhat.com,
linux-kernel@vger.kernel.org, roland@redhat.com, kyle@redhat.com
Subject: Re: [PATCH/RFC] powerpc: avoid generating .eh_frame sections with gcc-4.4
Date: Tue, 24 Feb 2009 09:40:34 +0100 [thread overview]
Message-ID: <20090224084034.GA11847@uranus.ravnborg.org> (raw)
In-Reply-To: <20090224065112.GA6690@bombadil.infradead.org>
On Tue, Feb 24, 2009 at 01:51:12AM -0500, Kyle McMartin wrote:
> From: Kyle McMartin <kyle@redhat.com>
>
> On ppc64 (at least) gcc-4.4 is defaulting to generating .eh_frame
> sections, which are, for the kernel, fairly pointless. Additionally, on
> ppc64 this generates a relocation format which the kernel module loader
> does not currently support (R_PPC64_REL32.)
>
> Alexandre Oliva verifies that -fno-dwarf2-cfi-asm prevents this
> .eh_frame section from being generated.
>
> These seem to be used for unwinding, but it doesn't look like we
> currently use them anywhere. (In fact, we explicitly dump them in the
> x86_64 linker script.)
A grep for "eh_frame" shows too many hits in the kernel to convince
me this is true.
arch/m32r/kernel/vmlinux.lds.S: from .altinstructions and .eh_frame */
arch/mn10300/kernel/vmlinux.lds.S: from .altinstructions and .eh_frame */
arch/parisc/kernel/vmlinux.lds.S: * from .altinstructions and .eh_frame
arch/powerpc/kernel/vdso32/sigtramp.S: .section .eh_frame,"a",@progbits
arch/powerpc/kernel/vdso32/vdso32.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr) } :text :eh_frame_hdr
arch/powerpc/kernel/vdso32/vdso32.lds.S: .eh_frame : { KEEP (*(.eh_frame)) }:text
arch/powerpc/kernel/vdso32/vdso32.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/powerpc/kernel/vdso64/sigtramp.S: .section .eh_frame,"a",@progbits
arch/powerpc/kernel/vdso64/vdso64.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr) } :text :eh_frame_hdr
arch/powerpc/kernel/vdso64/vdso64.lds.S: .eh_frame : { KEEP (*(.eh_frame)) }:text
arch/powerpc/kernel/vdso64/vdso64.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/s390/kernel/vdso32/vdso32.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr) } :text :eh_frame_hdr
arch/s390/kernel/vdso32/vdso32.lds.S: .eh_frame : { KEEP (*(.eh_frame)) } :text
arch/s390/kernel/vdso32/vdso32.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/s390/kernel/vdso64/vdso64.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr) } :text :eh_frame_hdr
arch/s390/kernel/vdso64/vdso64.lds.S: .eh_frame : { KEEP (*(.eh_frame)) } :text
arch/s390/kernel/vdso64/vdso64.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/sh/kernel/vsyscall/vsyscall-sigreturn.S: .section .eh_frame,"a",@progbits
arch/sh/kernel/vsyscall/vsyscall-trapa.S: * fill out .eh_frame -- PFM. */
arch/sh/kernel/vsyscall/vsyscall-trapa.S: .section .eh_frame,"a",@progbits
arch/sh/kernel/vsyscall/vsyscall.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr ) } :text :eh_frame_hdr
arch/sh/kernel/vsyscall/vsyscall.lds.S: .eh_frame : {
arch/sh/kernel/vsyscall/vsyscall.lds.S: KEEP (*(.eh_frame))
arch/sh/kernel/vsyscall/vsyscall.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/um/include/asm/common.lds.S: from .altinstructions and .eh_frame */
arch/um/kernel/dyn.lds.S: .eh_frame : { KEEP (*(.eh_frame)) }
arch/x86/kernel/vmlinux_32.lds.S: from .altinstructions and .eh_frame */
arch/x86/kernel/vmlinux_64.lds.S: from .altinstructions and .eh_frame */
arch/x86/kernel/vmlinux_64.lds.S: *(.eh_frame)
arch/x86/vdso/vdso-layout.lds.S: .eh_frame_hdr : { *(.eh_frame_hdr) } :text :eh_frame_hdr
arch/x86/vdso/vdso-layout.lds.S: .eh_frame : { KEEP (*(.eh_frame)) } :text
arch/x86/vdso/vdso-layout.lds.S: eh_frame_hdr PT_GNU_EH_FRAME;
arch/x86/vdso/vdso32/int80.S: .section .eh_frame,"a",@progbits
arch/x86/vdso/vdso32/int80.S:VDSO32_vsyscall_eh_frame_size = 0x40
arch/x86/vdso/vdso32/int80.S: .space VDSO32_vsyscall_eh_frame_size-(.LENDFDEDLSI-.LSTARTFRAMEDLSI), 0
arch/x86/vdso/vdso32/sigreturn.S: .section .eh_frame,"a",@progbits
arch/x86/vdso/vdso32/syscall.S: .section .eh_frame,"a",@progbits
arch/x86/vdso/vdso32/syscall.S:VDSO32_vsyscall_eh_frame_size = 0x40
arch/x86/vdso/vdso32/syscall.S: .space VDSO32_vsyscall_eh_frame_size-(.LENDFDE1-.LSTARTFRAME), 0
arch/x86/vdso/vdso32/sysenter.S: .section .eh_frame,"a",@progbits
arch/x86/vdso/vdso32/sysenter.S: * Emit a symbol with the size of this .eh_frame data,
arch/x86/vdso/vdso32/sysenter.S:VDSO32_vsyscall_eh_frame_size = (.LENDFDEDLSI-.LSTARTFRAMEDLSI)
x86 has a specific ".section .eh_frame,"a",@progbits" in vdso32/int80.S as one example.
Have you analyzed all these hits?
Sam
next prev parent reply other threads:[~2009-02-24 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 6:51 [PATCH/RFC] powerpc: avoid generating .eh_frame sections with gcc-4.4 Kyle McMartin
2009-02-24 8:40 ` Sam Ravnborg [this message]
2009-02-24 11:25 ` Alexandre Oliva
2009-02-24 17:48 ` Kyle McMartin
2009-02-24 23:36 ` Roland McGrath
2009-02-25 5:47 ` Sam Ravnborg
2009-02-25 5:46 ` Kyle McMartin
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=20090224084034.GA11847@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=aoliva@redhat.com \
--cc=kyle@infradead.org \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=roland@redhat.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).