Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Leo Yan" <leo.yan@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v7 23/23] selftests: Include tools Makefile.include
Date: Tue, 02 Jun 2026 15:15:36 +0000	[thread overview]
Message-ID: <20260602151536.9C6001F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260602-tools_build_fix_zero_init-v7-23-631baf679fe7@arm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Including `tools/scripts/Makefile.include` inside `tools/testing/selftests/lib.mk` breaks normal assignments to `EXTRA_CFLAGS` in selftest Makefiles, causing silent loss of compiler flags and test coverage.
--

commit 969534670ab7ca5eb2e61c1ef0a49417bd7e304d
Author: Leo Yan <leo.yan@arm.com>

selftests: Include tools Makefile.include

This commit includes tools/scripts/Makefile.include from selftests/lib.mk
to reuse LLVM cross-build validation and flags. It aims to improve Clang
cross builds by deriving cross-compile options directly from the GCC
cross toolchain.

> diff --git a/tools/testing/selftests/lib.mk b/tools/testing/selftests/lib.mk
> index f02cc8a2e4ae3..e2e2d8aa57280 100644
> --- a/tools/testing/selftests/lib.mk
> +++ b/tools/testing/selftests/lib.mk
> @@ -1,11 +1,17 @@
[ ... ]
> +selfdir = $(realpath $(dir $(filter %/lib.mk,$(MAKEFILE_LIST))))
> +top_srcdir = $(selfdir)/../../..
> +
> +include $(top_srcdir)/tools/scripts/Makefile.include

[Severity: Medium]
Does including Makefile.include here break EXTRA_CFLAGS assignments in
individual selftest makefiles?

tools/scripts/Makefile.include modifies EXTRA_CFLAGS using the override
directive:

override EXTRA_CFLAGS += $(FLAG_ZERO_INIT)

According to GNU Make semantics, once a variable has been appended using
override, any subsequent normal assignments without override are ignored.

For example, tools/testing/selftests/x86/Makefile attempts to append
flags later:

EXTRA_CFLAGS += -DCAN_BUILD_32

Because of the earlier override, this normal assignment is silently dropped.
Consequently, tests like single_step_syscall.c evaluate #ifdef CAN_BUILD_32
as false in main(), silently skipping 32-bit specific test coverage.

Could this be resolved by either removing the override in Makefile.include
or updating selftest makefiles to also use override for EXTRA_CFLAGS?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260602-tools_build_fix_zero_init-v7-0-631baf679fe7@arm.com?part=23

      reply	other threads:[~2026-06-02 15:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 14:40 [PATCH v7 00/23] tools build: Append -fzero-init-padding-bits=all option Leo Yan
2026-06-02 14:40 ` [PATCH v7 01/23] tools: lib: thermal: Fix typo Leo Yan
2026-06-02 14:54   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 02/23] tools/thermal: " Leo Yan
2026-06-02 14:52   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 03/23] tools: lib: thermal: Initialize CFLAGS before including Makefile.include Leo Yan
2026-06-02 14:56   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 04/23] tools/thermal: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 05/23] selftests/nolibc: Use a dedicated cross cc-option helper Leo Yan
2026-06-02 15:02   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 06/23] tools build: Append -fzero-init-padding-bits=all to extra cflags Leo Yan
2026-06-02 15:04   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 07/23] perf build: Append extra host flags Leo Yan
2026-06-02 14:40 ` [PATCH v7 08/23] tools build: Append extra host CFLAGS for fixdep Leo Yan
2026-06-02 15:00   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 09/23] tools: bootconfig: Append extra cflags Leo Yan
2026-06-02 14:40 ` [PATCH v7 10/23] tools: counter: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 11/23] tools: dma: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 12/23] tools: gpio: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 13/23] tools: hv: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 14/23] tools: iio: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 15/23] tools: mm: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 16/23] tools: objtool: Append extra host cflags Leo Yan
2026-06-02 14:40 ` [PATCH v7 17/23] tools: power: acpi: Append extra cflags Leo Yan
2026-06-02 15:07   ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 18/23] tools: power: x86/intel-speed-select: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 19/23] tools: sched_ext: " Leo Yan
2026-06-02 21:27   ` Tejun Heo
2026-06-02 14:40 ` [PATCH v7 20/23] tools: spi: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 21/23] tools: tracing: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 22/23] tools: usb: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 23/23] selftests: Include tools Makefile.include Leo Yan
2026-06-02 15:15   ` sashiko-bot [this message]

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=20260602151536.9C6001F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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