public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dl9pf@gmx.de (Jan-Simon Möller)
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, 09 Jul 2014 13:24:04 +0200	[thread overview]
Message-ID: <1485533.R9kdQa9l1r@aragorn> (raw)
In-Reply-To: <20140709095718.GD9485@arm.com>

Hi Will,


> BTW, have you tried building an arm64 kernel with clang?

ragarding arm64: yes, there is a test target already - see  
http://git.linuxfoundation.org/?p=llvmlinux.git;a=tree;f=targets/vexpress64

Reproduce with:
git clone http://git.linuxfoundation.org/llvmlinux.git
cd llvmlinux/targets/vexpress64
make


Best,
Jan-Simon

  reply	other threads:[~2014-07-09 11:24 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 at converseincode.com
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 ` [PATCH 2/6] arm: LLVMLinux: Use current_stack_pointer to calculate pt_regs address behanw at converseincode.com
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 ` [PATCH 4/6] arm: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
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 ` [PATCH 6/6] arm: LLVMLinux: Use current_stack_pointer in unwind_backtrace behanw at converseincode.com
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 11:24   ` Jan-Simon Möller [this message]
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=1485533.R9kdQa9l1r@aragorn \
    --to=dl9pf@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox