From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: clang-built-linux <clang-built-linux@googlegroups.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
lkft-triage@lists.linaro.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>
Subject: [next] x86_64 defconfig failed with clang-10
Date: Fri, 14 May 2021 23:42:44 +0530 [thread overview]
Message-ID: <CA+G9fYvYxqVhUTkertjZjcrUq8LWPnO7qC==Wum3gYCwWF9D6Q@mail.gmail.com> (raw)
My two cents,
We know clang-10 support is stopped, but our build system is still running
these builds with clang-10. one of those observations is,
The LKFT build failures were noticed while building x86_64 and i386 with
clang-10 on linux next-20210514 tag.
- x86_64 (defconfig) with clang-10 - FAIL
- i386 (defconfig) with clang-10 - FAIL
- x86_64 (defconfig) with clang-11 - PASS
- i386 (defconfig) with clang-11 - PASS
- x86_64 (defconfig) with clang-12 - PASS
- i386 (defconfig) with clang-12 - PASS
Build log:
----------
make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=x86_64
CROSS_COMPILE=x86_64-linux-gnu- 'HOSTCC=sccache clang' 'CC=sccache
clang'
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool:
eb_relocate_parse_slow()+0x427: stack state mismatch: cfa1=4+120
cfa2=-1+0
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool:
eb_copy_relocations()+0x1d5: stack state mismatch: cfa1=4+104
cfa2=-1+0
x86_64-linux-gnu-ld: arch/x86/kernel/kprobes/opt.o: in function
`arch_prepare_optimized_kprobe':
opt.c:(.text+0x798): undefined reference to `__compiletime_assert_251'
make[1]: *** [/builds/linux/Makefile:1272: vmlinux] Error 1
ref:
https://builds.tuxbuild.com/1sW0ag5finSjVuErrrzeunjj1nx/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2021-05-14 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 18:12 Naresh Kamboju [this message]
2021-05-14 20:54 ` [next] x86_64 defconfig failed with clang-10 Nathan Chancellor
2021-05-17 20:39 ` Nick Desaulniers
2021-05-18 0:55 ` Nathan Chancellor
2021-05-18 1:04 ` Hyeonggon Yoo
2021-05-18 1:11 ` Hyeonggon Yoo
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='CA+G9fYvYxqVhUTkertjZjcrUq8LWPnO7qC==Wum3gYCwWF9D6Q@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sfr@canb.auug.org.au \
/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.