Repository navigation
Use latest Oscan release compiler - #57
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 1a3dd721-b278-42b6-9431-d8a8525dc5b6
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
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.
Release builds were pinned to Oscan 0.0.43, so newer compiler releases were not picked up automatically.
This resolves the latest published Oscan tag once and passes it to every platform build. Windows and Linux build that tagged source with the C and Cranelift backends, then use the matching C package's bundled toolchain for hosted C bridges and linking. This avoids depending on the provider DLL removed from Oscan's toolchain-free LLVM package in v0.0.45 while preserving hosted builds. macOS continues to use the matching C package directly.
Resolving the tag once keeps the compiler version consistent across the full build matrix, even if a new Oscan release appears while the workflow is running.