From: John Hubbard <jhubbard@nvidia.com>
To: <jarkko.sakkinen@iki.fi>
Cc: <akpm@linux-foundation.org>, <andreyknvl@google.com>,
<ast@kernel.org>, <clang-built-linux@googlegroups.com>,
<daniel@iogearbox.net>, <elver@google.com>, <jarkko@kernel.org>,
<keescook@chromium.org>, <linux-kernel@vger.kernel.org>,
<masahiroy@kernel.org>, <miguel.ojeda.sandonis@gmail.com>,
<natechancellor@gmail.com>, <ndesaulniers@google.com>,
<sedat.dilek@gmail.com>, <vincenzo.frascino@arm.com>,
<will@kernel.org>, John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH v3 1/7] compiler-clang: add build check for clang 10.0.1
Date: Mon, 16 Nov 2020 19:04:27 -0800 [thread overview]
Message-ID: <20201117030427.61981-1-jhubbard@nvidia.com> (raw)
In-Reply-To: <20201104013447.GA21728@kapsi.fi>
Hi,
I just ran into this and it's a real pain to figure out, because even
with the very latest Fedora 33 on my test machine, which provides clang
version 11.0.0:
$ clang --version
clang version 11.0.0 (Fedora 11.0.0-2.fc33)
Target: x86_64-unknown-linux-gnu
...the bpftrace program still chokes on some, but not all commands, in
ways that invisible to normal debugging. For example:
$ sudo bpftrace -e 'tracepoint:syscalls:sys_enter_vmsplice { @[kstack()]
= count(); }'
/lib/modules/5.10.0-rc4-hubbard-github+/source/include/linux/compiler-clang.h:12:3:
error: Sorry, your version of Clang is too old - please use 10.0.1 or
newer.
But Jarkko's recommended fix works! In other words, applying the diff
below fixes it for me. So I'm replying in order to note that the problem
is real and hoping that the fix is applied soon.
diff --git a/include/linux/compiler-clang.h b/include/linux/compiler-clang.h
index dd7233c48bf3..c2228b957fd7 100644
--- a/include/linux/compiler-clang.h
+++ b/include/linux/compiler-clang.h
@@ -7,9 +7,11 @@
+ __clang_minor__ * 100 \
+ __clang_patchlevel__)
+#ifndef __BPF_TRACING__
#if CLANG_VERSION < 100001
# error Sorry, your version of Clang is too old - please use 10.0.1 or newer.
#endif
+#endif
/* Compiler specific definitions for Clang compiler */
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2020-11-17 3:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 22:59 [PATCH v3 0/7] set clang minimum version to 10.0.1 Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 1/7] compiler-clang: add build check for clang 10.0.1 Nick Desaulniers
2020-11-03 4:55 ` Jarkko Sakkinen
2020-11-03 6:38 ` Nathan Chancellor
2020-11-03 9:00 ` Jarkko Sakkinen
2020-11-03 18:48 ` Nick Desaulniers
2020-11-04 0:38 ` Jarkko Sakkinen
2020-11-04 1:18 ` Nick Desaulniers
2020-11-04 1:34 ` Jarkko Sakkinen
2020-11-04 1:36 ` Jarkko Sakkinen
2020-11-17 3:04 ` John Hubbard [this message]
2020-11-17 18:46 ` Nick Desaulniers
2020-11-18 2:31 ` Nathan Chancellor
2020-11-18 2:37 ` Andrew Morton
2020-09-02 22:59 ` [PATCH v3 2/7] Revert "kbuild: disable clang's default use of -fmerge-all-constants" Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 3/7] Revert "arm64: bti: Require clang >= 10.0.1 for in-kernel BTI support" Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 4/7] Revert "arm64: vdso: Fix compilation with clang older than 8" Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 5/7] Partially revert "ARM: 8905/1: Emit __gnu_mcount_nc when using Clang 10.0.0 or newer" Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 6/7] kasan: Remove mentions of unsupported Clang versions Nick Desaulniers
2020-09-02 22:59 ` [PATCH v3 7/7] compiler-gcc: improve version error Nick Desaulniers
2020-09-07 21:25 ` Will Deacon
2020-09-03 14:06 ` [PATCH v3 0/7] set clang minimum version to 10.0.1 Sedat Dilek
2020-09-03 17:28 ` Nathan Chancellor
2020-09-04 5:42 ` Miguel Ojeda
2020-09-07 16:12 ` Arvind Sankar
2020-09-08 4:42 ` Nathan Chancellor
2020-09-07 21:26 ` Will Deacon
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=20201117030427.61981-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=ast@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@iogearbox.net \
--cc=elver@google.com \
--cc=jarkko.sakkinen@iki.fi \
--cc=jarkko@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sedat.dilek@gmail.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®