From: Will Deacon <will.deacon@arm.com>
To: "behanw@converseincode.com" <behanw@converseincode.com>
Cc: "anurag19aggarwal@gmail.com" <anurag19aggarwal@gmail.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"charlebm@gmail.com" <charlebm@gmail.com>,
"dave.long@linaro.org" <dave.long@linaro.org>,
"k.khlebnikov@samsung.com" <k.khlebnikov@samsung.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linyongting@gmail.com" <linyongting@gmail.com>,
Nikolay Borisov <Nikolay.Borisov@arm.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rabin@rab.in" <rabin@rab.in>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Wed, 9 Jul 2014 10:57:18 +0100 [thread overview]
Message-ID: <20140709095718.GD9485@arm.com> (raw)
In-Reply-To: <1404850576-2006-1-git-send-email-behanw@converseincode.com>
On Tue, Jul 08, 2014 at 09:16:10PM +0100, behanw@converseincode.com wrote:
> From: Behan Webster <behanw@converseincode.com>
>
> 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).
>
> Clang only supports global named registers for non-allocatable registers like
> the stack pointer. By centralizing the definition of current_stack_pointer, the
> use of named registers for ARM remains largely unchanged while working for both
> gcc and clang.
All looks sane to me. For the series:
Acked-by: Will Deacon <will.deacon@arm.com>
BTW, have you tried building an arm64 kernel with clang?
Will
next prev parent reply other threads:[~2014-07-09 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 20:16 [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw
2014-07-08 20:16 ` [PATCH 1/6] arm: LLVMLinux: Add global named register current_stack_pointer for ARM behanw
2014-07-08 20:16 ` [PATCH 2/6] arm: LLVMLinux: Use current_stack_pointer to calculate pt_regs address behanw
2014-07-08 20:16 ` [PATCH 3/6] arm: LLVMLinux: Use current_stack_pointer for return_address behanw
2014-07-08 20:16 ` [PATCH 4/6] arm: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw
2014-07-08 20:16 ` [PATCH 5/6] arm: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw
2014-07-08 20:16 ` [PATCH 6/6] arm: LLVMLinux: Use current_stack_pointer in unwind_backtrace behanw
2014-07-09 9:57 ` Will Deacon [this message]
2014-07-09 11:24 ` [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Jan-Simon Möller
2014-07-13 9:10 ` Nicolas Pitre
2014-07-17 4:17 ` Behan Webster
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=20140709095718.GD9485@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Nikolay.Borisov@arm.com \
--cc=anurag19aggarwal@gmail.com \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=dave.long@linaro.org \
--cc=dwmw2@infradead.org \
--cc=k.khlebnikov@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linyongting@gmail.com \
--cc=rabin@rab.in \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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