Release archive
Kalandra 0.99.1 — ARM64 and cross-compilation
Linux and Windows ARM64, Raspberry Pi and five CPU destinations from one compiler download.
Kalandra 0.99.1 adds native Linux ARM64 and Windows ARM64 support, and CPU cross-compilation across all five supported platforms. This page covers the changes since 0.99.0. The macOS distribution continues to support mixed CPU/Metal development.
Linux ARM64 and Raspberry Pi
The compiler, language server and generated applications now run natively on Linux ARM64. Choose kalandra-native-cpu-standalone-linux-arm64.tar.gz for Ubuntu 24.04 or a compatible system with glibc 2.39 or newer.
For Raspberry Pi 3, 4, 5 and Zero 2 W, use a 64-bit Raspberry Pi OS Trixie installation. Bookworm is too old for the packaged toolchain. This is ARMv8-A CPU support; 32-bit systems and VideoCore GPU execution are not included. Qualification covers native ARM64 runners and official Raspberry Pi OS userspace, rather than physical Pi boards and their firmware or kernel variants.
Windows ARM64
The compiler, editor tools, language server and generated applications run natively on Windows 11 ARM64. Choose kalandra-native-cpu-standalone-windows-arm64.tar.gz and install Visual Studio 2026 ARM64 C++ tools with the Windows SDK. Compile from an ARM64-targeting developer shell.
The pinned Windows ARM64 toolchain has no ASan, UBSan or TSan runtimes. Sanitizer options fail explicitly; normal and optimized builds retain arithmetic, bounds, ownership and task checks.
One download, five CPU destinations
Install the standalone compiler package for your build machine. CPU and mixed CPU/Metal packages include runtime data for Linux x86-64, Linux ARM64, Windows x86-64, Windows ARM64 and macOS ARM64, plus host-native linkers. You do not need a destination compiler executable for each platform.
Select the destination using --platform linux-x86_64, linux-arm64, windows-x86_64, windows-arm64 or macos-arm64. Reusable --toolchain profiles can configure your SDK paths. Only the selected runtime is linked into your program; the alternatives increase download and disk size without adding execution overhead or emulation.
macOS targets require macOS 26 or newer on Apple silicon. This path uses Kalandra-owned system import declarations, so Linux and Windows build hosts need no Apple SDK or separate LLVM installation. Your applications receive an ad hoc signature; Developer ID signing and notarization remain separate distribution steps.
Linux destinations still require GNU development libraries and startup objects. Windows destinations still require the Windows SDK and MSVC CRT link libraries. These system development libraries are not bundled. The cross-compilation guide includes complete commands, SDK configuration and reusable profiles.
Correctness and ABI safety
Destination-specific layouts, calling conventions, stack access, record and closure allocation, and task lowering now follow the selected CPU ABI. Runtime versions, checksums, object architectures and macOS deployment compatibility are checked before linking. Rejected configurations and failed links preserve existing output files.
All 20 cross-compilation directions passed 63 programs each on native destination runners: 1,260 executions covering all ten numeric types, tensor operations, recursion, owned values, tasks, cancellation and fault behavior. Each executable and each combined host distribution was reproduced independently. These checks qualify correctness and portability; they are not new performance measurements.
Install and update
Download your build host's package from the v0.99.1 GitHub release. On macOS, choose the standalone Metal DMG for mixed CPU/GPU development or the CPU-only DMG. Standalone DMGs are Developer ID signed, notarized and stapled. Linux and Windows archives are available for both x86-64 and ARM64.
Verify the SHA-256 sidecar, keep the complete toolchain directory together and add its bin directory to PATH. kalandra --version reports 0.99.1. Existing native compilation defaults retain their system-toolchain requirements; explicit cross-platform builds use the bundled host linker and target runtime.
Download kalandra-native.vsix from the same release. Install it using VS Code's Extensions: Install from VSIX command and select your installed kalandra-lsp in Kalandra Native: Server Path. The extension keeps its independent version, 0.1.0; the native language server reports 0.99.1. Other LSP editors can launch the same server over standard input/output. No Node.js or npm installation is required by the native tools or installed editor client.
Release scope
There are no numerical or cancellation-contract changes in this release. Cross-compilation supports the CPU backend, not Metal kernel compilation or cross-target sanitizers. macOS x86-64, 32-bit targets, CUDA, Vulkan and FreeBSD distribution qualification are not included. Existing macOS Metal requirements remain Xcode 26.2 and the pinned Metal Toolchain component.