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 05/23] selftests/nolibc: Use a dedicated cross cc-option helper
Date: Tue, 02 Jun 2026 15:02:07 +0000	[thread overview]
Message-ID: <20260602150208.2321E1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260602-tools_build_fix_zero_init-v7-5-631baf679fe7@arm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Renaming `cc-option` to `cross-cc-option` in `Makefile.nolibc` breaks compiler flag probing in `Makefile.include` during cross-builds with Clang.
--

commit 2287b14b38d381104f1caab4547ea009ec49cae7
Author: Leo Yan <leo.yan@arm.com>

selftests/nolibc: Use a dedicated cross cc-option helper

This commit renames the nolibc cc-option helper to cross-cc-option to ensure
CLANG_CROSS_FLAGS is used for architecture-specific flag probes. This keeps
cross-build checks explicit and avoids clashing with the common tools helper.

> diff --git a/tools/testing/selftests/nolibc/Makefile.nolibc b/tools/testing/selftests/nolibc/Makefile.nolibc
> --- a/tools/testing/selftests/nolibc/Makefile.nolibc
> +++ b/tools/testing/selftests/nolibc/Makefile.nolibc
> @@ -23,7 +23,7 @@ include $(srctree)/scripts/subarch.include
>  ARCH = $(SUBARCH)
>  endif
>  
> -cc-option = $(call __cc-option, $(CC),$(CLANG_CROSS_FLAGS),$(1),$(2))
> +cross-cc-option = $(call __cc-option, $(CC),$(CLANG_CROSS_FLAGS),$(1),$(2))

[Severity: Medium]
Does this change break compiler flag probing in Makefile.include during
cross-builds with Clang?

Since cc-option is no longer overridden to include $(CLANG_CROSS_FLAGS) here,
uses of cc-option in Makefile.include will fall back to the generic cc-option
defined in scripts/Makefile.compiler.

For example, Makefile.include evaluates:

__CFLAGS_STACKPROTECTOR = $(call cc-option,-fstack-protector-all) \
    $(call cc-option,-mstack-protector-guard=global)

Because CC is left as just clang without any target flags in this context,
the generic cc-option will probe the host compiler instead of the target
compiler. Could this discard valid target flags if the host doesn't support
them, altering test coverage and breaking feature enablement for the nolibc
test suite?

[ ... ]

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

  reply	other threads:[~2026-06-02 15:02 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 [this message]
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

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=20260602150208.2321E1F00893@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