From: Clark Williams <clrkwllms@kernel.org>
To: linux-rt-users@vger.kernel.org
Cc: David Abdurachmanov <davidlt@rivosinc.com>, luffyluo@lysander
Date: Wed, 7 Jan 2026 16:54:52 -0600 [thread overview]
Message-ID: <aV7kPP8QkU-rZ4G2@lysander> (raw)
<luffyluo@tencent.com>, Wander Lairson Costa <wander@redhat.com>
Bcc:
Subject: [ANNOUNCE] stalld v1.26.1 released
Reply-To:
Hi all,
I'm pleased to announce the release of stalld v1.26.1, now available
at kernel.org, GitLab, and GitHub.
Overview
This release focuses on build system improvements, adding RISC-V
64-bit architecture support and enhancing cross-platform compatibility
through better compiler flag detection.
New Architecture Support
RISC-V 64-bit (riscv64)
- stalld can now be built for RISC-V 64-bit systems
- Adds to existing support for x86_64, aarch64, s390x, i686, and
powerpc/ppc64le
Build System Improvements (Wander Lairson Costa)
Compiler Flag Detection
- Added feature detection for -mno-omit-leaf-frame-pointer, fixing
builds on s390x and older compilers
- Improved -fcf-protection detection using direct compiler testing
instead of GCC version checks
- Removed redundant GCC version check, simplifying the Makefile
Build Process
- BPF tool versions (kernel, clang, bpftool) now printed during build
for easier debugging of compilation issues
- Explicit 'test' target in tests directory for clearer build process
Bug Fixes
- Fixed typo: renamed 'merge_taks_info' to 'merge_tasks_info'
- Updated .gitignore to exclude development tool metadata
Download
- https://git.kernel.org/pub/scm/utils/stalld/stalld.git
- https://gitlab.com/rt-linux-tools/stalld
- https://github.com/clrkwllms/stalld
git tag: v1.26.1
Contributors
- David Abdurachmanov
- luffyluo
- Wander Lairson Costa
- Clark Williams
Full release notes: doc/RELEASE_NOTES_v1.26.1.md
Best regards,
Clark Williams
--
The United States Coast Guard
Ruining Natural Selection since 1790
reply other threads:[~2026-01-07 22:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aV7kPP8QkU-rZ4G2@lysander \
--to=clrkwllms@kernel.org \
--cc=davidlt@rivosinc.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=luffyluo@lysander \
/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