From: Andrew Morton <akpm@osdl.org>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: sam@ravnborg.org, benh@kernel.crashing.org, ak@muc.de,
paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_UNWIND_INFO
Date: Sun, 15 Jan 2006 23:46:18 -0800 [thread overview]
Message-ID: <20060115234618.6745a7c8.akpm@osdl.org> (raw)
In-Reply-To: <43CB5B15.76F0.0078.0@novell.com>
"Jan Beulich" <JBeulich@novell.com> wrote:
>
> >>> Sam Ravnborg <sam@ravnborg.org> 14.01.06 15:03:01 >>>
> >On Sat, Jan 14, 2006 at 04:56:35AM -0800, Andrew Morton wrote:
> >>
> >> > Index: linux/Makefile
> >> > ===================================================================
> >> > --- linux.orig/Makefile
> >> > +++ linux/Makefile
> >> > @@ -502,6 +502,10 @@ CFLAGS += $(call add-align,CONFIG_CC_AL
> >> > CFLAGS += $(call add-align,CONFIG_CC_ALIGN_LOOPS,-loops)
> >> > CFLAGS += $(call add-align,CONFIG_CC_ALIGN_JUMPS,-jumps)
> >> >
> >> > +ifdef CONFIG_UNWIND_INFO
> >> > +CFLAGS += -fasynchronous-unwind-tables
> >> > +endif
> >Is this option available on all gcc's for all archs?
> >Otherwise you have to do:
> >CFLAGS += $(call cc-option,-fasynchronous-unwind-tables,)
>
> Yes, it is (and it has been at least since 3.2.x). Apparently the PPC backend doesn't fully support this...
>
And others might not support it either. We don't know.
Perhaps this option should be enabled only on architectures where it's known
to work, rather than disabled only on ppc64, as my fix does.
next prev parent reply other threads:[~2006-01-16 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:59 Jan Beulich
2006-01-14 12:56 ` Andrew Morton
2006-01-14 14:03 ` Sam Ravnborg
2006-01-16 7:36 ` Jan Beulich
2006-01-16 7:46 ` Andrew Morton [this message]
2006-01-18 11:48 ` Paul Mackerras
2006-01-18 15:18 ` Andi Kleen
2006-01-18 15:58 ` Jan Beulich
2006-01-18 16:11 ` Andi Kleen
2006-01-18 16:48 ` Jan Beulich
2006-01-20 4:47 ` Paul Mackerras
2006-01-20 6:13 ` Andi Kleen
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=20060115234618.6745a7c8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=JBeulich@novell.com \
--cc=ak@muc.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®