Changes in Makefile.include

814d051e - tools/build: Use SYSTEM_BPFTOOL for system bpftool

Wed, 26 Mar 2025 00:40:18 +0000

tools/build: Use SYSTEM_BPFTOOL for system bpftoolThe feature test for system bpftool uses BPFTOOL as the variable to setits path, defaulting to just "bpftool" if not set by the user.This conflicts with selftests and a few other utilities, which expectBPFTOOL to be set to the in-tree bpftool path by default. For example,bpftool selftests fail to build:$ make -C tools/testing/selftests/bpf/make: Entering directory '/home/tglozar/dev/linux/tools/testing/selftests/bpf'make: *** No rule to make target 'bpftool', needed by '/home/tglozar/dev/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h'. Stop.make: Leaving directory '/home/tglozar/dev/linux/tools/testing/selftests/bpf'Fix the problem by renaming the variable used for system bpftool fromBPFTOOL to SYSTEM_BPFTOOL, so that the new usage does not conflict withthe existing one of BPFTOOL.Cc: John Kacur Cc: Luis Goncalves Link: https://lore.kernel.org/20250326004018.248357-1-tglozar@redhat.comFixes: 8a635c3856dd ("tools/build: Add bpftool-skeletons feature test")Closes: https://lore.kernel.org/linux-kernel/5df6968a-2e5f-468e-b457-fc201535dd4c@linux.ibm.com/Reported-by: Venkat Rao Bagalkote Tested-by: Venkat Rao Bagalkote Suggested-by: Quentin Monnet Acked-by: Quentin Monnet Signed-off-by: Tomas Glozar Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/tools/scripts/Makefile.include

8a635c38 - tools/build: Add bpftool-skeletons feature test

Tue, 18 Feb 2025 14:58:53 +0000

tools/build: Add bpftool-skeletons feature testAdd bpftool-skeletons feature test, testing the presence of a bpftoolcapable of generating skeletons.This is to be used for tools that do not require building their ownbootstrap bpftool from the kernel source tree.Cc: John Kacur Cc: Luis Goncalves Cc: Gabriele Monaco Cc: Clark Williams Link: https://lore.kernel.org/20250218145859.27762-3-tglozar@redhat.comSigned-off-by: Tomas Glozar Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/tools/scripts/Makefile.include

293f324c - tools: Unify top-level quiet infrastructure

Thu, 13 Feb 2025 21:06:21 +0000

tools: Unify top-level quiet infrastructureCommit f2868b1a66d4f40f ("perf tools: Expose quiet/verbose variables inMakefile.perf") moved the quiet infrastructure out oftools/build/Makefile.build and into the top-level Makefile.perf file sothat the quiet infrastructure could be used throughout perf and not justin Makefile.build.Extract out the quiet infrastructure into Makefile.include so that itcan be leveraged outside of perf.Fixes: f2868b1a66d4f40f ("perf tools: Expose quiet/verbose variables in Makefile.perf")Reviewed-by: Jiri Olsa Signed-off-by: Charlie Jenkins Acked-by: Andrii Nakryiko Cc: Adrian Hunter Cc: Alexander Shishkin Cc: Alexei Starovoitov Cc: Benjamin Tissoires Cc: Daniel Borkmann Cc: Daniel Lezcano Cc: Eduard Zingerman Cc: Hao Luo Cc: Ian Rogers Cc: Ingo Molnar Cc: Jiri Kosina Cc: John Fastabend Cc: Josh Poimboeuf Cc: KP Singh Cc: Lukasz Luba Cc: Mark Rutland Cc: Martin KaFai Lau Cc: Mykola Lysenko Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Quentin Monnet Cc: Rafael J. Wysocki Cc: Shuah Khan Cc: Song Liu Cc: Stanislav Fomichev Cc: Steven Rostedt (VMware) Cc: Yonghong Song Cc: Zhang Rui Link: https://lore.kernel.org/r/20250213-quiet_tools-v3-1-07de4482a581@rivosinc.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/scripts/Makefile.include

c2bd08ba - treewide: remove meaningless assignments in Makefiles

Wed, 21 Feb 2024 13:42:01 +0000

treewide: remove meaningless assignments in MakefilesIn Makefiles, $(error ), $(warning ), and $(info ) expand to the emptystring, as explained in the GNU Make manual [1]: "The result of the expansion of this function is the empty string."Therefore, they are no-op except for logging purposes.$(shell ...) expands to the output of the command. It expands to theempty string when the command does not print anything to stdout.Hence, $(shell mkdir ...) is no-op except for creating the directory.Remove meaningless assignments.[1]: https://www.gnu.org/software/make/manual/make.html#Make-Control-FunctionsSigned-off-by: Masahiro Yamada Reviewed-by: Arnaldo Carvalho de Melo Reviewed-by: Ian Rogers Link: https://lore.kernel.org/r/20240221134201.2656908-1-masahiroy@kernel.orgSigned-off-by: Namhyung Kim Cc: Mark Rutland Cc: Peter Zijlstra Cc: Adrian Hunter Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Alexander Shishkin Cc: Ingo Molnar Cc: linux-kbuild@vger.kernel.orgCc: linux-kernel@vger.kernel.orgCc: linux-perf-users@vger.kernel.org List of files: /linux-6.15/tools/scripts/Makefile.include

b5c532e9 - tools/build: Fix -s detection code in tools/scripts/Makefile.include

Sun, 08 Oct 2023 21:22:51 +0000

tools/build: Fix -s detection code in tools/scripts/Makefile.includeAs Dmitry described in [1] changelog the current way of detecting-s option is broken for new make.Changing the tools/build -s option detection the same way as it wasfixed for root Makefile in [1].[1] 4bf73588165b ("kbuild: Port silent mode detection to future gnu make.")Cc: Dmitry Goncharov Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Acked-by: Namhyung Kim Cc: Peter Zijlstra Cc: KP Singh Cc: Martin KaFai Lau Cc: Song Liu Cc: Yonghong Song Cc: John Fastabend Cc: Hao Luo Cc: Ian Rogers Cc: Stanislav Fomichev Cc: Daniel Borkmann Cc: Quentin Monnet Cc: Arnaldo Carvalho de Melo Cc: Andrii Nakryiko Cc: Alexei Starovoitov Cc: Ingo Molnar Cc: Alexander Shishkin Cc: bpf@vger.kernel.orgCc: linux-perf-users@vger.kernel.orgLink: https://lore.kernel.org/r/20231008212251.236023-3-jolsa@kernel.orgSigned-off-by: Namhyung Kim List of files: /linux-6.15/tools/scripts/Makefile.include

b539a287 - selftests/bpf: Fix cross compilation with CLANG_CROSS_FLAGS

Fri, 17 Feb 2023 15:18:32 +0000

selftests/bpf: Fix cross compilation with CLANG_CROSS_FLAGSI cross-compile my BPF selftests with the following command:CLANG_CROSS_FLAGS="--target=aarch64-linux-gnu --sysroot=/sysroot/" \ make LLVM=1 CC=clang CROSS_COMPILE=aarch64-linux-gnu- SRCARCH=arm64(Note the use of CLANG_CROSS_FLAGS to specify a custom sysroot insteadof letting clang use gcc's default sysroot)However, CLANG_CROSS_FLAGS gets propagated to host tools builds (libbpfand bpftool) and because they reference it directly in their Makefiles,they end up cross-compiling host objects which results in linkingerrors.This patch ensures that CLANG_CROSS_FLAGS is reset if CROSS_COMPILEisn't set (for example when reaching a BPF host tool build).Signed-off-by: Florent Revest Link: https://lore.kernel.org/r/20230217151832.27784-1-revest@chromium.orgSigned-off-by: Alexei Starovoitov List of files: /linux-6.15/tools/scripts/Makefile.include

e9c28192 - kbuild: Make $(LLVM) more flexible

Fri, 04 Mar 2022 17:08:14 +0000

kbuild: Make $(LLVM) more flexibleThe LLVM make variable allows a developer to quickly switch between theGNU and LLVM tools. However, it does not handle versioned binaries, suchas the ones shipped by Debian, as LLVM=1 just defines the tool variableswith the unversioned binaries.There was some discussion during the review of the patch that introducesLLVM=1 around versioned binaries, ultimately coming to the conclusionthat developers can just add the folder that contains the unversionedbinaries to their PATH, as Debian's versioned suffixed binaries arereally just symlinks to the unversioned binaries in /usr/lib/llvm-#/bin:$ realpath /usr/bin/clang-14/usr/lib/llvm-14/bin/clang$ PATH=/usr/lib/llvm-14/bin:$PATH make ... LLVM=1However, that can be cumbersome to developers who are constantly testingseries with different toolchains and versions. It is simple enough tosupport these versioned binaries directly in the Kbuild system byallowing the developer to specify the version suffix with LLVM=, whichis shorter than the above suggestion:$ make ... LLVM=-14It does not change the meaning of LLVM=1 (which will continue to useunversioned binaries) and it does not add too much additional complexityto the existing $(LLVM) code, while allowing developers to quickly testtheir series with different versions of the whole LLVM suite of tools.Some developers may build LLVM from source but not add the binaries totheir PATH, as they may not want to use that toolchain systemwide.Support those developers by allowing them to supply the directory thatthe LLVM tools are available in, as it is no more complex to supportthan the version suffix change above.$ make ... LLVM=/path/to/llvm/Update and reorder the documentation to reflect these new additions.At the same time, notate that LLVM=0 is not the same as just omitting italtogether, which has confused people in the past.Link: https://lore.kernel.org/r/20200317215515.226917-1-ndesaulniers@google.com/Link: https://lore.kernel.org/r/20220224151322.072632223@infradead.org/Suggested-by: Masahiro Yamada Suggested-by: Peter Zijlstra Signed-off-by: Nathan Chancellor Reviewed-by: Kees Cook Reviewed-by: Nick Desaulniers Signed-off-by: Masahiro Yamada List of files: /linux-6.15/tools/scripts/Makefile.include

7fd9fd46 - tools: Fix unavoidable GCC call in Clang builds

Tue, 08 Mar 2022 12:14:28 +0000

tools: Fix unavoidable GCC call in Clang buildsIn ChromeOS and Gentoo we catch any unwanted mixed Clang/LLVMand GCC/binutils usage via toolchain wrappers which fail builds.This has revealed that GCC is called unconditionally in Clangconfigured builds to populate GCC_TOOLCHAIN_DIR.Allow the user to override CLANG_CROSS_FLAGS to avoid the GCCcall - in our case we set the var directly in the ebuild recipe.In theory Clang could be able to autodetect these settings sothis logic could be removed entirely, but in practice as thecommit cebdb7374577 ("tools: Help cross-building with clang")mentions, this does not always work, so giving distributionsmore control to specify their flags & sysroot is beneficial.Suggested-by: Manoj Gupta Suggested-by: Nathan Chancellor Signed-off-by: Adrian Ratiu Signed-off-by: Daniel Borkmann Acked-by: Nathan Chancellor Cc: Nick Desaulniers Link: https://lore.kernel.org/lkml/87czjk4osi.fsf@ryzen9.i-did-not-set--mail-host-address--so-tickle-meLink: https://lore.kernel.org/bpf/20220308121428.81735-1-adrian.ratiu@collabora.com List of files: /linux-6.15/tools/scripts/Makefile.include

b7892f7d - tools: Ignore errors from `which' when searching a GCC toolchain

Tue, 01 Feb 2022 09:31:20 +0000

tools: Ignore errors from `which' when searching a GCC toolchainWhen cross-building tools with clang, we run `which $(CROSS_COMPILE)gcc`to detect whether a GCC toolchain provides the standard libraries. It isonly a helper because some distros put libraries where LLVM does notautomatically find them. On other systems, LLVM detects the libcautomatically and does not need this. There, it is completely fine notto have a GCC at all, but some versions of `which' display an error whenthe command is not found: which: no aarch64-linux-gnu-gcc in ($PATH)Since the error can safely be ignored, throw it to /dev/null.Fixes: cebdb7374577 ("tools: Help cross-building with clang")Reported-by: Nathan Chancellor Signed-off-by: Jean-Philippe Brucker Signed-off-by: Daniel Borkmann Tested-by: Nathan Chancellor Reviewed-by: Nathan Chancellor Link: https://lore.kernel.org/bpf/20220201093119.1713207-1-jean-philippe@linaro.org List of files: /linux-6.15/tools/scripts/Makefile.include

cebdb737 - tools: Help cross-building with clang

Thu, 16 Dec 2021 16:38:38 +0000

tools: Help cross-building with clangCross-compilation with clang uses the -target parameter rather than atoolchain prefix. Just like the kernel Makefile, add that parameter toCFLAGS when CROSS_COMPILE is set.Unlike the kernel Makefile, we use the --sysroot and --gcc-toolchainoptions because unlike the kernel, tools require standard libraries.Commit c91d4e47e10e ("Makefile: Remove '--gcc-toolchain' flag") providessome background about --gcc-toolchain. Normally clang finds on its ownthe additional utilities and libraries that it needs (for example GNU ldor glibc). On some systems however, this autodetection doesn't work.There, our only recourse is asking GCC directly, and pass the result to--sysroot and --gcc-toolchain. Of course that only works when a crossGCC is available.Autodetection worked fine on Debian, but to use the aarch64-linux-gnutoolchain from Archlinux I needed both --sysroot (for crt1.o) and--gcc-toolchain (for crtbegin.o, -lgcc). The --prefix parameter wasn'tneeded there, but it might be useful on other distributions.Use the CLANG_CROSS_FLAGS variable instead of CLANG_FLAGS because itallows tools such as bpftool, that need to build both host and targetbinaries, to easily filter out the cross-build flags from CFLAGS.Signed-off-by: Jean-Philippe Brucker Signed-off-by: Andrii Nakryiko Acked-by: Quentin Monnet Acked-by: Nick Desaulniers Link: https://lore.kernel.org/bpf/20211216163842.829836-2-jean-philippe@linaro.org List of files: /linux-6.15/tools/scripts/Makefile.include

c6de37dd - tools build: Fix quiet cmd indentation

Wed, 21 Apr 2021 18:58:48 +0000

tools build: Fix quiet cmd indentationThe tools quiet cmd output has mismatched indentation (and extra spacecharacter between cmd name and target name) compared to the rest ofkbuild out: HOSTCC scripts/insert-sys-cert LD /srv/code/tools/objtool/arch/x86/objtool-in.o LD /srv/code/tools/objtool/libsubcmd-in.o AR /srv/code/tools/objtool/libsubcmd.a HOSTLD scripts/genksyms/genksyms CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o LD /srv/code/tools/objtool/objtool-in.o LINK /srv/code/tools/objtool/objtool HOSTLD scripts/mod/modpost CC kernel/bounds.sAdjust to match the rest of kbuild.Signed-off-by: Kees Cook Signed-off-by: Masahiro Yamada List of files: /linux-6.15/tools/scripts/Makefile.include

d1d1a2cd - tools: disable -Wno-type-limits

Fri, 07 May 2021 01:02:42 +0000

tools: disable -Wno-type-limitsPatch series "lib/find_bit: fast path for small bitmaps", v6.Bitmap operations are much simpler and faster in case of small bitmapswhich fit into a single word. In linux/bitmap.c we have a machinery thatallows compiler to replace actual function call with a few instructions ifbitmaps passed into the function are small and their size is known atcompile time.find_*_bit() API lacks this functionality; but users will benefit from ita lot. One important example is cpumask subsystem when NR_CPUS <=BITS_PER_LONG.This patch (of 12):GENMASK(h, l) may be passed with unsigned types. In such case,type-limits warning is generated for example in case of GENMASK(h, 0).Link: https://lkml.kernel.org/r/20210401003153.97325-1-yury.norov@gmail.comLink: https://lkml.kernel.org/r/20210401003153.97325-2-yury.norov@gmail.comSigned-off-by: Yury Norov Acked-by: Rasmus Villemoes Cc: Alexey Klimov Cc: Andy Shevchenko Cc: Arnd Bergmann Cc: David Sterba Cc: Dennis Zhou Cc: Geert Uytterhoeven Cc: Jianpeng Ma Cc: Joe Perches Cc: John Paul Adrian Glaubitz Cc: Josh Poimboeuf Cc: Rich Felker Cc: Stefano Brivio Cc: Wei Yang Cc: Wolfram Sang Cc: Yoshinori Sato Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/tools/scripts/Makefile.include

f62700ce - tools: Allow proper CC/CXX/... override with LLVM=1 in Makefile.include

Tue, 13 Apr 2021 15:34:19 +0000

tools: Allow proper CC/CXX/... override with LLVM=1 in Makefile.includeselftests/bpf/Makefile includes tools/scripts/Makefile.include.With the following command make -j60 LLVM=1 LLVM_IAS=1 <=== compile kernel make -j60 -C tools/testing/selftests/bpf LLVM=1 LLVM_IAS=1 V=1some files are still compiled with gcc. This patchfixed the case if CC/AR/LD/CXX/STRIP is allowed to beoverridden, it will be written to clang/llvm-ar/..., instead ofgcc binaries. The definition of CC_NO_CLANG is also relocatedto the place after the above CC is defined.Signed-off-by: Yonghong Song Signed-off-by: Alexei Starovoitov Link: https://lore.kernel.org/bpf/20210413153419.3028165-1-yhs@fb.com List of files: /linux-6.15/tools/scripts/Makefile.include

c9491aad - Documentation: Replace more lkml.org links with lore

Wed, 10 Feb 2021 23:40:05 +0000

Documentation: Replace more lkml.org links with loreAs started by commit 05a5f51ca566 ("Documentation: Replace lkml.orglinks with lore"), replace a few more scattered lkml.org links withlore to better use a single source that's more likely to stay availablelong-term.Signed-off-by: Kees Cook Link: https://lore.kernel.org/r/20210210234005.2236201-1-keescook@chromium.orgSigned-off-by: Jonathan Corbet List of files: /linux-6.15/tools/scripts/Makefile.include

211a741c - tools: Factor Clang, LLC and LLVM utils definitions

Thu, 28 Jan 2021 01:50:58 +0000

tools: Factor Clang, LLC and LLVM utils definitionsWhen dealing with BPF/BTF/pahole and DWARF v5 I wanted to build bpftool.While looking into the source code I found duplicate assignments in misc toolsfor the LLVM eco system, e.g. clang and llvm-objcopy.Move the Clang, LLC and/or LLVM utils definitions to tools/scripts/Makefile.includefile and add missing includes where needed. Honestly, I was inspired by the commitc8a950d0d3b9 ("tools: Factor HOSTCC, HOSTLD, HOSTAR definitions").I tested with bpftool and perf on Debian/testing AMD64 and LLVM/Clang v11.1.0-rc1.Build instructions:[ make and make-options ]MAKE="make V=1"MAKE_OPTS="HOSTCC=clang HOSTCXX=clang++ HOSTLD=ld.lld CC=clang LD=ld.lld LLVM=1 LLVM_IAS=1"MAKE_OPTS="$MAKE_OPTS PAHOLE=/opt/pahole/bin/pahole"[ clean-up ]$MAKE $MAKE_OPTS -C tools/ clean[ bpftool ]$MAKE $MAKE_OPTS -C tools/bpf/bpftool/[ perf ]PYTHON=python3 $MAKE $MAKE_OPTS -C tools/perf/I was careful with respecting the user's wish to override custom compiler, linker,GNU/binutils and/or LLVM utils settings.Signed-off-by: Sedat Dilek Signed-off-by: Daniel Borkmann Acked-by: Andrii Nakryiko Acked-by: Jiri Olsa # tools/build and tools/perfLink: https://lore.kernel.org/bpf/20210128015117.20515-1-sedat.dilek@gmail.com List of files: /linux-6.15/tools/scripts/Makefile.include

fbcdaa19 - perf build: Support build BPF skeletons with perf

Tue, 29 Dec 2020 21:42:13 +0000

perf build: Support build BPF skeletons with perfBPF programs are useful in perf to profile BPF programs.BPF skeleton is by far the easiest way to write BPF tools. Enablebuilding BPF skeletons in util/bpf_skel. A dummy bpf skeleton is added.More bpf skeletons will be added for different use cases.Signed-off-by: Song Liu Tested-by: Arnaldo Carvalho de Melo Acked-by: Jiri Olsa Acked-by: Namhyung Kim Cc: Alexander Shishkin Cc: Mark Rutland Cc: Peter Zijlstra Cc: kernel-team@fb.comLink: http://lore.kernel.org/lkml/20201229214214.3413833-3-songliubraving@fb.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/scripts/Makefile.include

c8a950d0 - tools: Factor HOSTCC, HOSTLD, HOSTAR definitions

Tue, 10 Nov 2020 16:43:05 +0000

tools: Factor HOSTCC, HOSTLD, HOSTAR definitionsSeveral Makefiles in tools/ need to define the host toolchain variables.Move their definition to tools/scripts/Makefile.includeSigned-off-by: Jean-Philippe Brucker Signed-off-by: Andrii Nakryiko Acked-by: Jiri Olsa Acked-by: Rafael J. Wysocki Link: https://lore.kernel.org/bpf/20201110164310.2600671-2-jean-philippe@linaro.org List of files: /linux-6.15/tools/scripts/Makefile.include

47c09d6a - bpftool: Introduce "prog profile" command

Mon, 09 Mar 2020 17:32:15 +0000

bpftool: Introduce "prog profile" commandWith fentry/fexit programs, it is possible to profile BPF program withhardware counters. Introduce bpftool "prog profile", which measures keymetrics of a BPF program.bpftool prog profile command creates per-cpu perf events. Then it attachesfentry/fexit programs to the target BPF program. The fentry program savesperf event value to a map. The fexit program reads the perf event again,and calculates the difference, which is the instructions/cycles used bythe target program.Example input and output: ./bpftool prog profile id 337 duration 3 cycles instructions llc_misses 4228 run_cnt 3403698 cycles (84.08%) 3525294 instructions # 1.04 insn per cycle (84.05%) 13 llc_misses # 3.69 LLC misses per million isns (83.50%)This command measures cycles and instructions for BPF program with id337 for 3 seconds. The program has triggered 4228 times. The rest of theoutput is similar to perf-stat. In this example, the counters were onlycounting ~84% of the time because of time multiplexing of perf counters.Note that, this approach measures cycles and instructions in very smallincrements. So the fentry/fexit programs introduce noticeable errors tothe measurement results.The fentry/fexit programs are generated with BPF skeletons. Therefore, webuild bpftool twice. The first time _bpftool is built without skeletons.Then, _bpftool is used to generate the skeletons. The second time, bpftoolis built with skeletons.Signed-off-by: Song Liu Signed-off-by: Daniel Borkmann Reviewed-by: Quentin Monnet Acked-by: Yonghong Song Link: https://lore.kernel.org/bpf/20200309173218.2739965-2-songliubraving@fb.com List of files: /linux-6.15/tools/scripts/Makefile.include

be40920f - tools: Let O= makes handle a relative path with -C option

Fri, 06 Mar 2020 18:32:58 +0000

tools: Let O= makes handle a relative path with -C optionWhen I tried to compile tools/perf from the top directory with the -Coption, the O= option didn't work correctly if I passed a relative path: $ make O=BUILD -C tools/perf/ make: Entering directory '/home/mhiramat/ksrc/linux/tools/perf' BUILD: Doing 'make -j8' parallel build ../scripts/Makefile.include:4: *** O=/home/mhiramat/ksrc/linux/tools/perf/BUILD does not exist. Stop. make: *** [Makefile:70: all] Error 2 make: Leaving directory '/home/mhiramat/ksrc/linux/tools/perf'The O= directory existence check failed because the check script ran inthe build target directory instead of the directory where I ran the makecommand.To fix that, once change directory to $(PWD) and check O= directory,since the PWD is set to where the make command runs.Fixes: c883122acc0d ("perf tools: Let O= makes handle relative paths")Reported-by: Randy Dunlap Signed-off-by: Masami Hiramatsu Cc: Andrew Morton Cc: Borislav Petkov Cc: Geert Uytterhoeven Cc: Jiri Olsa Cc: Masahiro Yamada Cc: Michal Marek Cc: Peter Zijlstra Cc: Sasha Levin Cc: Steven Rostedt (VMware) Cc: stable@vger.kernel.orgLink: http://lore.kernel.org/lkml/158351957799.3363.15269768530697526765.stgit@devnote2Signed-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/scripts/Makefile.include

39e7317e - perf build: Do not use -Wshadow on gcc < 4.8

Fri, 19 Jul 2019 18:34:30 +0000

perf build: Do not use -Wshadow on gcc < 4.8As it is too strict, see https://lkml.org/lkml/2006/11/28/253 andhttps://gcc.gnu.org/gcc-4.8/changes.html, that takes into accountLinus's comments (search for Wshadow) for the reasoning about -Wshadownot being interesting before gcc 4.8.Acked-by: Andrii Nakryiko Cc: Adrian Hunter Cc: Jiri Olsa Cc: Namhyung Kim Link: https://lkml.kernel.org/r/20190719183417.GQ3624@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/scripts/Makefile.include