From: behanw@converseincode•com (Behan Webster)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Thu, 31 Jul 2014 21:11:59 -0700 [thread overview]
Message-ID: <53DB138F.7070709@converseincode.com> (raw)
In-Reply-To: <20140731103323.GL26853@arm.com>
On 07/31/14 03:33, Will Deacon wrote:
> On Thu, Jul 31, 2014 at 12:57:25AM +0100, behanw at converseincode.com wrote:
>> From: Behan Webster <behanw@converseincode•com>
>>
>> This patch set moves from using locally defined named registers to access the
>> stack pointer to using a globally defined named register. This allows the code
>> to work both with gcc and clang.
>>
>> The LLVMLinux project aims to fully build the Linux kernel using both gcc and
>> clang (the C front end for the LLVM compiler infrastructure project).
>>
>> Behan Webster (4):
>> arm64: LLVMLinux: Add current_stack_pointer() for arm64
>> arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk
>> arm64: LLVMLinux: Calculate current_thread_info from
>> current_stack_pointer
>> arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c
> Once Andreas's comments have been addressed:
>
> Acked-by: Will Deacon <will.deacon@arm•com>
>
> Please can you send a new series after the merge window?
Pity. I was hoping to get it in this merge window.
However, will resubmit for 3.18.
Thanks,
Behan
--
Behan Webster
behanw at converseincode.com
next prev parent reply other threads:[~2014-08-01 4:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 23:57 [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 1/4] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 2/4] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 3/4] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-07-31 5:31 ` Andreas Färber
2014-07-31 16:04 ` Behan Webster
2014-07-30 23:57 ` [PATCH 4/4] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-07-31 0:11 ` [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Olof Johansson
2014-07-31 10:33 ` Will Deacon
2014-07-31 15:39 ` Olof Johansson
2014-07-31 15:48 ` Will Deacon
2014-07-31 15:52 ` Olof Johansson
2014-08-01 4:11 ` Behan Webster [this message]
2014-08-26 14:16 ` Will Deacon
2014-08-27 4:26 ` Behan Webster
2014-08-27 4:29 ` [PATCH V2 0/6] " behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 1/6] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 2/6] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 3/6] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 4/6] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 5/6] arm64: LLVMLinux: Use global stack register variable for aarch64 behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 6/6] arm64: LLVMLinux: Use global stack pointer in return_address() behanw at converseincode.com
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=53DB138F.7070709@converseincode.com \
--to=behanw@converseincode$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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