From: Deepesh.Varatharajan@windriver.com
To: openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com,
Deepesh.Varatharajan@windriver.com
Subject: [RFC 0/4] Oe-selftest for Clang, LLVM, LLD
Date: Tue, 3 Feb 2026 06:03:24 -0800 [thread overview]
Message-ID: <20260203140337.1971735-1-Deepesh.Varatharajan@windriver.com> (raw)
From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
This patch series introduces a test framework to run selftests for both
native and target builds of Clang, LLVM, and LLD.
Summary of changes:
-Patch 1: Disable clang-tools-extra tests because Clang's CMake cannot
see the llvm-bcanalyzer target.
-Patch 2: Enabled the required CMake flags for clang, llvm & lld tests
-Patch 3: Selftest script for Clang, LLVM, and LLD including exclude list
-Patch 4: Fix rust build failure by replacing target llvm-config with native
Testing:
1. The test suite has been successfully validated on x86-64, arm64, riscv64,
and arm32 for all three components.
2. Clang, LLVM & LLD all together ~80K tests are there and we currently
~200 tests to exclude list which are failing (0.25%).
WIP:
LLVM target tests are currently failing on x86. This is under investigation
and will be addressed
Deepesh Varatharajan (4):
clang-tools-extra: disable tests
clang: Enable tests for llvm, clang, lld
oeqa/selftest/clang: Add selftest for Clang/LLVM/LLD
rust: Fix rust build failure
meta/lib/oeqa/selftest/cases/clang.py | 301 ++++++++++++++++++
.../0042-guard-clang-tools-extra-test.patch | 74 +++++
meta/recipes-devtools/clang/clang_git.bb | 3 +-
meta/recipes-devtools/clang/common.inc | 1 +
meta/recipes-devtools/clang/lld_git.bb | 2 +-
meta/recipes-devtools/clang/llvm_git.bb | 11 +-
meta/recipes-devtools/rust/rust_1.92.0.bb | 5 +-
7 files changed, 389 insertions(+), 8 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/clang.py
create mode 100644 meta/recipes-devtools/clang/clang/0042-guard-clang-tools-extra-test.patch
--
2.49.0
next reply other threads:[~2026-02-03 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 14:03 Deepesh.Varatharajan [this message]
2026-02-03 14:03 ` [RFC 1/4] clang-tools-extra: disable tests Deepesh.Varatharajan
2026-02-03 14:03 ` [RFC 2/4] clang: Enable tests for llvm, clang, lld Deepesh.Varatharajan
2026-02-03 16:08 ` [OE-core] " Peter Kjellerstedt
2026-02-04 5:34 ` Deepesh Varatharajan
2026-02-03 14:03 ` [RFC 3/4] oeqa/selftest/clang: Add selftest for Clang/LLVM/LLD Deepesh.Varatharajan
2026-02-03 14:03 ` [RFC 4/4] rust: Fix rust build failure Deepesh.Varatharajan
2026-02-12 16:34 ` [RFC 0/4] Oe-selftest for Clang, LLVM, LLD Deepesh Varatharajan
2026-02-12 18:01 ` [OE-core] " Alexander Kanavin
2026-02-15 8:54 ` Mathieu Dubois-Briand
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=20260203140337.1971735-1-Deepesh.Varatharajan@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.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