From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: [PATCH 0/9] perf build: Fix builds with clang and BUILD_NONDISTRO
Date: Tue, 15 Sep 2026 23:12:09 -0700 [thread overview]
Message-ID: <20260916061218.3061216-1-irogers@google.com> (raw)
Several perf build configurations are broken, and stayed broken because
the build test suite doesn't cover them.
Three of them fail outright:
$ make CC=clang BUILD_NONDISTRO=1
util/libbfd.c:56:1: error: mutex 'bfd_mutex' is still held at the end
of function [-Werror,-Wthread-safety-analysis]
$ make BUILD_NONDISTRO=1 NO_DEMANGLE=1
util/symbol.c:2714: error: 'DMGL_PARAMS' undeclared
$ make CC=clang-19
*** Specify CROSS_COMPILE or add CLANG_TARGET_FLAGS for x86_64
A fourth is worse for being silent. "make CC=clang" appends clang's
--target= and -fintegrated-as to CXX, but CXX is only set to clang++ by
"make LLVM=1", so it is still g++ and rejects both. Feature tests are
allowed to fail, so nothing is reported: the build succeeds and just
quietly drops libllvm and C++ demangling support.
$ make CC=clang && grep LIBLLVM .config-detected
(nothing, whereas a gcc build reports CONFIG_LIBLLVM=y)
The patches are grouped as:
1-2 Fix the two build failures, in libbfd.c and symbol.c.
3-4 Include the headers that are used directly rather than relying
on other headers to drag them in. No functional change.
5-7 Fix the clang handling in Makefile.config: don't give clang's
flags to a non-clang CXX, and use the CC that was asked for
instead of hard coding "clang" when picking the target triple
and when testing the compiler version.
8 Remove three build test entries left behind by the removal of
the options they tested. None of them define what to build, so
each silently repeats "make_pure" and the suite spends six
builds appearing to cover options that no longer exist.
9 Add build tests for the configurations above, so they don't
break again. As a build that loses a feature still succeeds,
the clang tests also check that libLLVM is still built in.
Testing:
- 13 build configurations (gcc, clang, versioned clang, LLVM=1,
BUILD_NONDISTRO, NO_DEMANGLE, NO_LIBDW, NO_LIBELF, DEBUG, asan,
refcount checking) pass, where two failed before the series.
- Every patch builds on its own, so the series stays bisectable.
- Each fix was confirmed by reintroducing the bug and checking that
the test added in patch 9 fails:
CXX flags given to g++ make_clang fails on libLLVM
libbfd thread safety make_clang_nondistro fails to compile
symbol.c demangling make_nondistro_no_demangle likewise
Ian Rogers (9):
perf libbfd: Fix the clang -Wthread-safety build failure
perf symbol: Fix the build when demangling with libbfd
perf libbfd: Include the headers that are used
perf pmu: Include the headers that are used
perf build: Only pass clang flags to CXX when CXX is clang
perf build: Use the given CC rather than clang in clang builds
perf build: Check the version of the compiler that is used
perf build: Remove leftovers of removed build options
perf test: Add build tests for clang and libbfd demangling
tools/perf/Makefile.config | 13 +++++++---
tools/perf/Makefile.perf | 3 ---
tools/perf/tests/make | 50 ++++++++++++++++++++++++++++++++++----
tools/perf/util/Build | 2 +-
tools/perf/util/libbfd.c | 41 ++++++++++++++++++++++++++-----
tools/perf/util/libbfd.h | 9 +++++++
tools/perf/util/pmu.c | 5 +++-
tools/perf/util/symbol.c | 18 +++++++++++---
8 files changed, 119 insertions(+), 22 deletions(-)
base-commit: 91b0782fc9e9d2f0a40b5256146e014802fdbb36
--
2.55.0.1032.g73a4cd73de-goog
next reply other threads:[~2026-09-16 6:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 6:12 Ian Rogers [this message]
2026-09-16 6:12 ` [PATCH 1/9] perf libbfd: Fix the clang -Wthread-safety build failure Ian Rogers
2026-09-16 6:18 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 2/9] perf symbol: Fix the build when demangling with libbfd Ian Rogers
2026-09-16 6:21 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 3/9] perf libbfd: Include the headers that are used Ian Rogers
2026-09-16 6:22 ` sashiko-bot
2026-09-16 15:54 ` Ian Rogers
2026-09-16 17:37 ` Namhyung Kim
2026-09-16 6:12 ` [PATCH 4/9] perf pmu: " Ian Rogers
2026-09-16 6:14 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 5/9] perf build: Only pass clang flags to CXX when CXX is clang Ian Rogers
2026-09-16 6:17 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 6/9] perf build: Use the given CC rather than clang in clang builds Ian Rogers
2026-09-16 6:19 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 7/9] perf build: Check the version of the compiler that is used Ian Rogers
2026-09-16 6:16 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 8/9] perf build: Remove leftovers of removed build options Ian Rogers
2026-09-16 6:17 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 9/9] perf test: Add build tests for clang and libbfd demangling Ian Rogers
2026-09-16 6:22 ` sashiko-bot
2026-09-16 17:35 ` [PATCH 0/9] perf build: Fix builds with clang and BUILD_NONDISTRO Namhyung Kim
2026-09-22 12:47 ` Arnaldo Carvalho de Melo
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=20260916061218.3061216-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
/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.