All of lore.kernel.org
 help / color / mirror / Atom feed
From: behanw@converseincode.com (Behan Webster)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: LLVMLinux: Calculate pt_regs address from fp
Date: Fri, 06 Sep 2013 19:02:52 -0400	[thread overview]
Message-ID: <522A5F1C.400@converseincode.com> (raw)
In-Reply-To: <20130906221857.GQ6617@n2100.arm.linux.org.uk>

On 09/06/13 18:18, Russell King - ARM Linux wrote:
> On Fri, Sep 06, 2013 at 05:42:41PM -0400, behanw at converseincode.com wrote:
>> From: Behan Webster <behanw@converseincode.com>
>>
>> Use the frame pointer to calculate the end of the stack for current_pt_regs()
>> The existing code uses the stack pointer to do this calculation.
>> Using the frame pointer yeilds the same value in a more portable way.
>> This change supports being able to compile the kernel with gcc and clang.
> What happens when frame pointers are disabled on gcc?
Drat. Good point. Didn't think of that.

Could be rewritten to use current_stack_pointer (assuming the patch 
series that implements that would be amenable).

Thanks,

Behan

-- 
Behan Webster
behanw at converseincode.com

      reply	other threads:[~2013-09-06 23:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 21:42 [PATCH] arm: LLVMLinux: Use __builtin_frame_address instead of named registers behanw at converseincode.com
2013-09-06 21:42 ` behanw
2013-09-06 21:42 ` [PATCH] arm: LLVMLinux: Calculate pt_regs address from fp behanw at converseincode.com
2013-09-06 21:42   ` behanw
2013-09-06 22:18   ` Russell King - ARM Linux
2013-09-06 22:18     ` Russell King - ARM Linux
2013-09-06 23:02     ` Behan Webster [this message]

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=522A5F1C.400@converseincode.com \
    --to=behanw@converseincode.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.