From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Steven Rostedt <srostedt@redhat.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/3] powerpc, Makefile: Make it possible to safely select CONFIG_FRAME_POINTER
Date: Sat, 2 May 2009 04:14:43 +0400 [thread overview]
Message-ID: <20090502001443.GA2762@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090405210756.GG24374@uranus.ravnborg.org>
On Sun, Apr 05, 2009 at 11:07:56PM +0200, Sam Ravnborg wrote:
> On Fri, Mar 20, 2009 at 07:44:29PM +0300, Anton Vorontsov wrote:
> > This patch introduces ARCH_HAS_NORMAL_FRAME_POINTERS Kconfig symbol.
> > When defined, the top level Makefile won't add -fno-omit-frame-pointer
> > cflag (the flag is useless in PowerPC kernels, and also makes gcc
> > generate wrong code).
> >
> > Also move ARCH_WANT_FRAME_POINTERS's help text.
> >
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>
> Hi Anton - sorry for the late feedback.
>
> 1) The preferred naming for variables that are supposed to be selcted
> are "HAVE_xxxx".
> So in this case it would be:
> HAVE_NORMAL_FRAME_POINTER
OK, will rename.
> 2) I do not really understand the interpretation of normal in this case,
> can it be more specific?
Normal means that architecture's ABI implies having a framepointer,
we don't need any gcc flags.
I'm not sure if we can name it any better, that is what was
suggested by Steven and I don't have any better variant. ;-)
> Looking at your patch then if specified we use "-fomit-frame-pointer"
> in the case where it is set.
No. We specify neither -fomit-frame-pointer, nor we specify
-fno-omit-frame-pointer (because that flag causes gcc to generate
wrong code).
> So I read it like:
>
> If arch has normal framepointer then we omit them - strange?
>
> 3) Indent in top-level MAkefile for new stuff is generally 8 spaces.
> Do NOT use tabs as this would confuse make and rener assignmnet non-functional.
>
> 4) The individual "HAVE_* members should be sorted alphabetically in the arch
> Kconfig file (which they seldomly are :-( )
>
> Sam
Well, yes. So looking into the Kconfig, I'm quite unsure where
to put it to make it alphabetically correct. Ok, let's put
it after K. ;-)
Thanks!
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <srostedt@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] powerpc, Makefile: Make it possible to safely select CONFIG_FRAME_POINTER
Date: Sat, 2 May 2009 04:14:43 +0400 [thread overview]
Message-ID: <20090502001443.GA2762@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090405210756.GG24374@uranus.ravnborg.org>
On Sun, Apr 05, 2009 at 11:07:56PM +0200, Sam Ravnborg wrote:
> On Fri, Mar 20, 2009 at 07:44:29PM +0300, Anton Vorontsov wrote:
> > This patch introduces ARCH_HAS_NORMAL_FRAME_POINTERS Kconfig symbol.
> > When defined, the top level Makefile won't add -fno-omit-frame-pointer
> > cflag (the flag is useless in PowerPC kernels, and also makes gcc
> > generate wrong code).
> >
> > Also move ARCH_WANT_FRAME_POINTERS's help text.
> >
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>
> Hi Anton - sorry for the late feedback.
>
> 1) The preferred naming for variables that are supposed to be selcted
> are "HAVE_xxxx".
> So in this case it would be:
> HAVE_NORMAL_FRAME_POINTER
OK, will rename.
> 2) I do not really understand the interpretation of normal in this case,
> can it be more specific?
Normal means that architecture's ABI implies having a framepointer,
we don't need any gcc flags.
I'm not sure if we can name it any better, that is what was
suggested by Steven and I don't have any better variant. ;-)
> Looking at your patch then if specified we use "-fomit-frame-pointer"
> in the case where it is set.
No. We specify neither -fomit-frame-pointer, nor we specify
-fno-omit-frame-pointer (because that flag causes gcc to generate
wrong code).
> So I read it like:
>
> If arch has normal framepointer then we omit them - strange?
>
> 3) Indent in top-level MAkefile for new stuff is generally 8 spaces.
> Do NOT use tabs as this would confuse make and rener assignmnet non-functional.
>
> 4) The individual "HAVE_* members should be sorted alphabetically in the arch
> Kconfig file (which they seldomly are :-( )
>
> Sam
Well, yes. So looking into the Kconfig, I'm quite unsure where
to put it to make it alphabetically correct. Ok, let's put
it after K. ;-)
Thanks!
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-05-02 0:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 16:44 [PATCH v4 0/3] Tracers vs. CALLER_ADDR on PowerPC Anton Vorontsov
2009-03-20 16:44 ` Anton Vorontsov
2009-03-20 16:44 ` [PATCH 1/3] powerpc, Makefile: Make it possible to safely select CONFIG_FRAME_POINTER Anton Vorontsov
2009-03-20 16:44 ` Anton Vorontsov
2009-03-21 3:49 ` Steven Rostedt
2009-03-21 3:49 ` Steven Rostedt
2009-03-28 10:48 ` Anton Vorontsov
2009-03-28 10:48 ` Anton Vorontsov
2009-03-29 22:54 ` Benjamin Herrenschmidt
2009-03-29 22:54 ` Benjamin Herrenschmidt
2009-03-30 4:36 ` Sam Ravnborg
2009-03-30 4:36 ` Sam Ravnborg
2009-04-05 21:07 ` Sam Ravnborg
2009-04-05 21:07 ` Sam Ravnborg
2009-04-13 15:51 ` Steven Rostedt
2009-04-13 15:51 ` Steven Rostedt
2009-05-02 0:14 ` Anton Vorontsov [this message]
2009-05-02 0:14 ` Anton Vorontsov
2009-03-20 16:44 ` [PATCH 2/3] powerpc: Remove -fno-omit-frame-pointer workarounds Anton Vorontsov
2009-03-20 16:44 ` Anton Vorontsov
2009-03-21 3:50 ` Steven Rostedt
2009-03-21 3:50 ` Steven Rostedt
2009-03-20 16:44 ` [PATCH 3/3] tracing: Tracers that use CALLER_ADDR macros should select FRAME_POINTER Anton Vorontsov
2009-03-20 16:44 ` Anton Vorontsov
2009-03-20 16:52 ` [PATCH v4 0/3] Tracers vs. CALLER_ADDR on PowerPC Anton Vorontsov
2009-03-20 16:52 ` Anton Vorontsov
-- strict thread matches above, loose matches on Subject: below --
2009-05-02 0:13 [PATCH v5 " Anton Vorontsov
2009-05-02 0:14 ` [PATCH 1/3] powerpc, Makefile: Make it possible to safely select CONFIG_FRAME_POINTER Anton Vorontsov
2009-05-02 0:14 ` Anton Vorontsov
2009-05-02 19:48 ` Segher Boessenkool
2009-05-02 19:48 ` Segher Boessenkool
2009-05-03 2:04 ` Steven Rostedt
2009-05-03 2:04 ` Steven Rostedt
2009-05-05 7:56 ` Segher Boessenkool
2009-05-05 7:56 ` Segher Boessenkool
2009-05-05 13:33 ` Steven Rostedt
2009-05-05 13:33 ` Steven Rostedt
2009-05-05 13:51 ` Segher Boessenkool
2009-05-05 13:51 ` Segher Boessenkool
2009-05-05 23:11 ` Steven Rostedt
2009-05-05 23:11 ` Steven Rostedt
2009-05-18 4:14 ` Benjamin Herrenschmidt
2009-05-18 4:14 ` Benjamin Herrenschmidt
2009-05-18 19:55 ` Segher Boessenkool
2009-05-18 19:55 ` Segher Boessenkool
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=20090502001443.GA2762@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
--cc=srostedt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.