From: behanw@converseincode.com (Behan Webster)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Wed, 16 Jul 2014 21:17:43 -0700 [thread overview]
Message-ID: <53C74E67.9050401@converseincode.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1407130508580.3647@knanqh.ubzr>
On 07/13/14 02:10, Nicolas Pitre wrote:
> On Tue, 8 Jul 2014, behanw at 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.
> You verified that the compiled code is identical on gcc?
Yes. Identical.
> If so:
>
> Acked-by: Nicolas Pitre <nico@linaro.org>
Thanks,
Behan
--
Behan Webster
behanw at converseincode.com
WARNING: multiple messages have this Message-ID (diff)
From: Behan Webster <behanw@converseincode.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: anurag19aggarwal@gmail.com, catalin.marinas@arm.com,
charlebm@gmail.com, dave.long@linaro.org,
k.khlebnikov@samsung.com, linux@arm.linux.org.uk,
linyongting@gmail.com, Nikolay.Borisov@arm.com,
tglx@linutronix.de, u.kleine-koenig@pengutronix.de,
will.deacon@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rabin@rab.in, rostedt@goodmis.org,
dwmw2@infradead.org
Subject: Re: [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Wed, 16 Jul 2014 21:17:43 -0700 [thread overview]
Message-ID: <53C74E67.9050401@converseincode.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1407130508580.3647@knanqh.ubzr>
On 07/13/14 02:10, Nicolas Pitre wrote:
> On Tue, 8 Jul 2014, 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.
> You verified that the compiled code is identical on gcc?
Yes. Identical.
> If so:
>
> Acked-by: Nicolas Pitre <nico@linaro.org>
Thanks,
Behan
--
Behan Webster
behanw@converseincode.com
next prev parent reply other threads:[~2014-07-17 4:17 UTC|newest]
Thread overview: 22+ 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 at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 1/6] arm: LLVMLinux: Add global named register current_stack_pointer for ARM behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 2/6] arm: LLVMLinux: Use current_stack_pointer to calculate pt_regs address behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 3/6] arm: LLVMLinux: Use current_stack_pointer for return_address behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 4/6] arm: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 5/6] arm: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-08 20:16 ` [PATCH 6/6] arm: LLVMLinux: Use current_stack_pointer in unwind_backtrace behanw at converseincode.com
2014-07-08 20:16 ` behanw
2014-07-09 9:57 ` [PATCH 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Will Deacon
2014-07-09 9:57 ` Will Deacon
2014-07-09 11:24 ` Jan-Simon Möller
2014-07-09 11:24 ` Jan-Simon Möller
2014-07-13 9:10 ` Nicolas Pitre
2014-07-13 9:10 ` Nicolas Pitre
2014-07-17 4:17 ` Behan Webster [this message]
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=53C74E67.9050401@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.