From: "Jan Beulich" <JBeulich@novell.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Andi Kleen" <ak@muc.de>, "Andrew Morton" <akpm@osdl.org>,
"Paul Mackerras" <paulus@samba.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CONFIG_UNWIND_INFO
Date: Mon, 16 Jan 2006 08:36:37 +0100 [thread overview]
Message-ID: <43CB5B15.76F0.0078.0@novell.com> (raw)
In-Reply-To: <20060114140301.GA8443@mars.ravnborg.org>
>>> 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...
Jan
next prev parent reply other threads:[~2006-01-16 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:59 [PATCH] CONFIG_UNWIND_INFO Jan Beulich
2006-01-14 12:56 ` Andrew Morton
2006-01-14 14:03 ` Sam Ravnborg
2006-01-16 7:36 ` Jan Beulich [this message]
2006-01-16 7:46 ` Andrew Morton
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=43CB5B15.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--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