Nathan Chancellor natechancellor@gmail.com writes:
On Mon, Feb 11, 2019 at 11:45:20AM -0800, Kevin Hilman wrote:
[ + Nathan Chancellor ]
"kernelci.org bot" bot@kernelci.org writes:
next-clang/master build: 4 builds: 2 failed, 2 passed, 40 errors, 414 warnings (next-20190211)
Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...
Tree: next-clang Branch: master Git Describe: next-20190211 Git Commit: d4104460aec152e23cf80ab1f950f414bf94f4ea Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Built: 1 unique architecture
Build Failures Detected:
arm64: clang version 8.0.0-svn352860-1~exp1~20190201113135.15 (branches/release_80)
allmodconfig: FAIL defconfig: FAIL
Errors and Warnings Detected:
arm64: clang version 8.0.0-svn352860-1~exp1~20190201113135.15 (branches/release_80)
allmodconfig: 20 errors, 363 warnings allnoconfig: 3 warnings defconfig: 20 errors, 45 warnings tinyconfig: 3 warnings
Errors summary:
2 fatal error: too many errors emitted, stopping now [-ferror-limit=] 2 arch/arm64/lib/xor-neon.c:58:28: error: incompatible pointer types assigning to 'const unsigned long *' from 'uint64_t *' (aka 'unsigned long long *') [-Werror,-Wincompatible-pointer-types]
These look like the same issues that Nathan Chancellor fixed for arm32[1].
Kevin
[1] https://lore.kernel.org/lkml/20190126040111.9013-1-natechancellor@gmail.com/...
Hi Kevin,
This is actually https://github.com/ClangBuiltLinux/linux/issues/283.
We're waiting to hear back from the Clang maintainer to see what he has to say because it's not a straight forward fix.
I've hidden that warning from the one translation unit in the meantime, given that we know it's an issue and it should be fixed soon. I'm not sure if you have a system in place to temporarily apply patches like this (or if you would even want to) but it would help us uncover further issues.
https://raw.githubusercontent.com/nathanchance/patches/6cd3168b7a145/linux/b...
In general, we're trying not to maintain out-of-tree patches like this, but for a work-in-progress clang, I'm not really seeing any alternatives. We'll look into if/how we might do this in kernelCI.
Feel free to add me to future triage emails if you see fit.
@Matt Hart: could you add Nathan to the list of recipients for next-clang kernel builds?
Kevin