From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Michel Lespinasse <walken@google.com>
Subject: Re: [PATCH] Kconfig.debug: Add FRAME_POINTER anti-dependency for ARC
Date: Mon, 2 Sep 2013 12:02:55 +0300 [thread overview]
Message-ID: <CAOtvUMcKprmyKdi-+TJNvCNqaDv=6WLxeATkJtFe+b1c1bSSGA@mail.gmail.com> (raw)
In-Reply-To: <1377592285-21148-1-git-send-email-vgupta@synopsys.com>
Hi,
On Tue, Aug 27, 2013 at 11:31 AM, Vineet Gupta
<Vineet.Gupta1@synopsys.com> wrote:
>
> Frame pointer on ARC doesn't serve the conventional purpose of stack
> unwinding due to the typical way ABI designates it's usage.
More out of curiosity to understand the platform better than actual
review - can you explain a little what
you meant by this statement?
Is this statement because of the use of write back mode with ld/st to
or not related?
Thanks,
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
gilad@benyossef.com
Israel Cell: +972-52-8260388
US Cell: +1-973-8260388
http://benyossef.com
"If you take a class in large-scale robotics, can you end up in a
situation where the homework eats your dog?"
-- Jean-Baptiste Queru
next prev parent reply other threads:[~2013-09-02 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:31 [PATCH] Kconfig.debug: Add FRAME_POINTER anti-dependency for ARC Vineet Gupta
2013-08-29 11:04 ` Vineet Gupta
2013-08-29 15:18 ` Dave Hansen
2013-08-30 4:25 ` Vineet Gupta
2013-08-30 7:48 ` Vineet Gupta
2013-08-30 15:20 ` Dave Hansen
2013-09-02 8:48 ` Vineet Gupta
2013-09-02 8:48 ` Vineet Gupta
2013-09-02 9:02 ` Gilad Ben-Yossef [this message]
2013-09-02 11:41 ` Vineet Gupta
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='CAOtvUMcKprmyKdi-+TJNvCNqaDv=6WLxeATkJtFe+b1c1bSSGA@mail.gmail.com' \
--to=gilad@benyossef.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@linaro.org \
--cc=walken@google.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.