Update LLVM version from 15/16 to 17 across K Framework #4854
+8
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update GitHub Actions workflows: llvm: 15/16 → 17 - Update Debian package dependencies: - control.jammy: clang-15→17, lld-15→17, llvm-15→17 - control.noble: clang-16→17, lld-16→17 (llvm-17 already correct) - Update install-build-deps: clang-15→17, lld-15→17, llvm-15-tools→17 - Update macOS Homebrew: llvm@15→17 - Update macos-envrc: llvm@15→17 - Update llvm-backend submodule to include LLVM 17 changes This migration aligns K Framework with LLVM 17 for improved performance and compatibility with newer toolchain features. Depends on: runtimeverification/llvm-backend#1214
- Revert Ubuntu Jammy builds back to LLVM 15 (not available in Ubuntu 22.04) - Update llvm-backend clang-tidy script to auto-detect available LLVM version - Fix Debian package dependencies to use consistent LLVM versions per Ubuntu release - Jammy (22.04): LLVM 15 (available in standard repos) - Noble (24.04): LLVM 17 (available in standard repos) This resolves the 'run-clang-tidy-17: command not found' error and Ubuntu Jammy package build failures by using the correct LLVM versions for each platform.
- Update release workflow to use LLVM 15 for Ubuntu Jammy builds - Fix kframework Jammy package dependencies to use clang-15, lld-15, llvm-15 - Maintain LLVM 17 for Ubuntu Noble builds (correct for Ubuntu 24.04) This ensures consistency between workflow configuration and package dependencies, resolving the mismatch that was causing test confusion.
automergerpr-permission-manager
bot
merged commit d5b9cbf
into
develop
18 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the LLVM version from 15/16 to 17 across the entire K Framework repository to align with modern toolchain requirements and improve performance.
This PR requires llvm-backend PR #1214 to be merged first.
The llvm-backend submodule changes are included in this PR, but the final merge should wait until the llvm-backend PR is merged and released to ensure proper dependency alignment.
Changes Made
GitHub Actions Workflows
.github/workflows/release.yml: Updated allllvm: 15/16→llvm: 17.github/workflows/test-pr.yml: Updated allllvm: 15→llvm: 17Debian Package Dependencies
package/debian/kframework/control.jammy:clang-15→clang-17lld-15→lld-17llvm-15→llvm-17package/debian/kframework/control.noble:clang-16→clang-17lld-16→lld-17llvm-17(already correct)Installation Scripts
install-build-deps: Updated Debian package installationclang-15→clang-17lld-15→lld-17llvm-15-tools→llvm-17-toolsmacOS Support
package/macos/brew-install-deps:llvm@15→llvm@17macos-envrc: Updated environment variables forllvm@17Submodule Updates
llvm-backend/src/main/native/llvm-backend: Updated to include LLVM 17 changes from PR #1214Testing Strategy
llvm@17Migration Benefits
Related PRs
Checklist
deps/llvm-backend_releaseafter llvm-backend release