LLVM / Luau / L3i alignment

blocked · reviewed 2026-09-28

campaign · blocked · reviewed 2026-09-28

Move every compiling DreamWeave build onto clang and lld matching rustc's LLVM, so L3i's cross-language LTO works everywhere it ships. The reference setup is rustc 1.98.1 with LLVM/clang/lld 22.1.8. StroggForge matches the LLVM major of whatever rustc a job uses rather than pinning that exact patch release. Blocked means nobody has signed off on the rollout yet, not that every build is failing.

FieldValue
ProjectsStroggForge, L3i / l3i, dream-ini, dream-soft-render
Versionnot assigned
Target datenot committed
PlatformsLinux x86_64, PortMaster ARM64 (opt-in), Android ARM64 (opt-in), macOS ARM64, macOS x86_64, Windows x86_64
Distributiongithub-releases, crates-io

Requirements#

RequirementTypeStateDetail
Replace PortMaster GCC/EL8 configuration with clang/lld and an EL9 sysroottaskdoneDone in the workflows: the PortMaster job cross-compiles with clang/lld and cross-language LTO against an EL9 sysroot, glibc 2.34. Whether the result runs on a device is the next requirement. Evidence: .github/workflows/rustGlobalBuild.yml:release-portmaster; Git commit e83a91c.
Prove the portable artifact on the intended device/runtimeartifactblockedNobody has run an LLVM-built PortMaster binary on a handheld yet. Link the Actions run, the readelf output and the device test when somebody does.
Audit and migrate every affected consumer's ref and Cargo compiler flagsciactiveConsumers pin anything from v40 to v48, so most have not received the LLVM changes. Cargo does not inherit a dependency's .cargo/config.toml: every l3i consumer carries its own clang, lld and linker-plugin-lto settings, and all three have to be right.
Resolve Android NDK versus rustc LLVM compatibilityplatformtodoThe Android job uses NDK r27c at API 23, while setup-llvm matches the host rustc's LLVM. Nobody knows yet whether those two produce bitcode that links together. Measure it before claiming Android works.
Record compatibility floor and migration resultsdocumentationactiveWrite down the new floor (EL9, glibc 2.34), what the EL8 retirement broke, how MSRV jobs pick their LLVM, and which devices were actually tested.