[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140731154803.GB26853@arm.com>
Date: Thu, 31 Jul 2014 16:48:03 +0100
From: Will Deacon <will.deacon@....com>
To: Olof Johansson <olof@...om.net>
Cc: "behanw@...verseincode.com" <behanw@...verseincode.com>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
"k.khlebnikov@...sung.com" <k.khlebnikov@...sung.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"takahiro.akashi@...aro.org" <takahiro.akashi@...aro.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"dwmw2@...radead.org" <dwmw2@...radead.org>
Subject: Re: [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be
compiled with clang/LLVM
On Thu, Jul 31, 2014 at 04:39:55PM +0100, Olof Johansson wrote:
> On Thu, Jul 31, 2014 at 3:33 AM, Will Deacon <will.deacon@....com> wrote:
> > On Thu, Jul 31, 2014 at 12:57:25AM +0100, behanw@...verseincode.com wrote:
> >> From: Behan Webster <behanw@...verseincode.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@....com>
> >
> > Please can you send a new series after the merge window?
>
> Given that the ARM64 KVM guys are still actively breaking -next, and
> this is considerably smaller and lower risk than that, I think you can
> take it for 3.17?
Hey, those breakages are in the kvm tree not the arm64 tree! I'd really
rather wait on these as I don't see the rush to get them in for 3.17 and
it's not beyond the realms of possibility that they could cause problems
for a particular version of GCC (at the very least, I'd need to re-run
all the testing I've been doing).
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists