linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: akpm@linux-foundation.org
Cc: ak@linux.intel.com, linuxppc-dev@ozlabs.org, andi@firstfloor.org,
	mmarek@suse.cz, kyle@mcmartin.ca
Subject: Re: [patch 2/2] kbuild: move -fno-dwarf2-cfi-asm to powerpc only
Date: Thu, 04 Feb 2010 10:22:19 +1100	[thread overview]
Message-ID: <1265239339.8287.126.camel@pasglop> (raw)
In-Reply-To: <201002022240.o12Me3aI018845@imap1.linux-foundation.org>

On Tue, 2010-02-02 at 14:40 -0800, akpm@linux-foundation.org wrote:
> From: Andi Kleen <andi@firstfloor.org>
> 
> Better dwarf2 unwind information is a good thing, it allows better
> debugging with kgdb and crash and helps systemtap.
> 
> Commit 003086497f07f7f1e67c0c295e261740f822b377 ("Build with
> -fno-dwarf2-cfi-asm") disabled some CFI information globally to work
> around a module loader bug on powerpc.
> 
> But this disables the better unwind tables for all architectures, not just
> powerpc.  Move the workaround to powerpc and also add a suitable comment
> that's it really a workaround.
> 
> This improves dwarf2 unwind tables on x86 at least.
> 
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> Cc: Kyle McMartin <kyle@mcmartin.ca>

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

Do you want me to carry that in powerpc-next ?

Cheers,
Ben.

> Cc: Michal Marek <mmarek@suse.cz>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  Makefile              |    3 ---
>  arch/powerpc/Makefile |    5 +++++
>  2 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff -puN Makefile~kbuild-move-fno-dwarf2-cfi-asm-to-powerpc-only Makefile
> --- a/Makefile~kbuild-move-fno-dwarf2-cfi-asm-to-powerpc-only
> +++ a/Makefile
> @@ -579,9 +579,6 @@ KBUILD_CFLAGS += $(call cc-option,-Wno-p
>  # disable invalid "can't wrap" optimizations for signed / pointers
>  KBUILD_CFLAGS	+= $(call cc-option,-fno-strict-overflow)
>  
> -# revert to pre-gcc-4.4 behaviour of .eh_frame
> -KBUILD_CFLAGS	+= $(call cc-option,-fno-dwarf2-cfi-asm)
> -
>  # conserve stack if available
>  KBUILD_CFLAGS   += $(call cc-option,-fconserve-stack)
>  
> diff -puN arch/powerpc/Makefile~kbuild-move-fno-dwarf2-cfi-asm-to-powerpc-only arch/powerpc/Makefile
> --- a/arch/powerpc/Makefile~kbuild-move-fno-dwarf2-cfi-asm-to-powerpc-only
> +++ a/arch/powerpc/Makefile
> @@ -112,6 +112,11 @@ KBUILD_CFLAGS += $(call cc-option,-mspe=
>  # kernel considerably.
>  KBUILD_CFLAGS += $(call cc-option,-funit-at-a-time)
>  
> +# FIXME: the module load should be taught about the additional relocs
> +# generated by this.
> +# revert to pre-gcc-4.4 behaviour of .eh_frame
> +KBUILD_CFLAGS	+= $(call cc-option,-fno-dwarf2-cfi-asm)
> +
>  # Never use string load/store instructions as they are
>  # often slow when they are implemented at all
>  KBUILD_CFLAGS		+= -mno-string
> _

  reply	other threads:[~2010-02-03 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 22:40 [patch 2/2] kbuild: move -fno-dwarf2-cfi-asm to powerpc only akpm
2010-02-03 23:22 ` Benjamin Herrenschmidt [this message]
2010-02-04 13:03   ` 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=1265239339.8287.126.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=kyle@mcmartin.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mmarek@suse.cz \
    /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).