[llvmlinux] clang fails on linux-next since commit 8bf705d13039
sedat.dilek at gmail.com
Tue Jul 31 07:24:09 UTC 2018
On Mon, Jul 30, 2018 at 6:35 PM, Nick Desaulniers
<ndesaulniers at google.com> wrote:
> On Mon, Jul 30, 2018 at 2:46 AM Mark Rutland <mark.rutland at arm.com> wrote:
>> On Mon, Jul 30, 2018 at 11:40:49AM +0200, Sedat Dilek wrote:
>> > What are your plans to have...
>> > 4d2b25f630c7 locking/atomics: Instrument cmpxchg_double*()
>> > f9881cc43b11 locking/atomics: Instrument xchg()
>> > df79ed2c0643 locking/atomics: Simplify cmpxchg() instrumentation
>> > 00d5551cc4ee locking/atomics/x86: Reduce arch_cmpxchg64*() instrumentation
>> > ...for example in Linux 4.18 or 4.17.y?
>> I have no plans to have these backported.
> If they help us compile with clang, we'll backport to 4.17, 4.14, 4.9,
> and 4.4 stable. From
> it sounds like that is the case.
The commit in Linus upstream tree is...
b06ed71a624b locking/atomic, asm-generic: Add asm-generic/atomic-instrumented.h
sdi at iniza:~/src/linux-kernel/linux$ git describe --contains b06ed71a624b
...so backporting makes sense for linux-stable-4.17.y?
- sed@ -
More information about the LLVMLinux