-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency: llvm-backend/src/main/native/llvm-backend #3728
Merged
rv-jenkins
merged 9 commits into
develop
from
_update-deps/runtimeverification/llvm-backend
Oct 19, 2023
Merged
Update dependency: llvm-backend/src/main/native/llvm-backend #3728
rv-jenkins
merged 9 commits into
develop
from
_update-deps/runtimeverification/llvm-backend
Oct 19, 2023
Conversation
This file contains 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
…de2d5a7ce869723967fe89d4fc
Baltoli
approved these changes
Oct 18, 2023
rv-jenkins
pushed a commit
to runtimeverification/llvm-backend
that referenced
this pull request
Oct 19, 2023
This PR is a hotfix for a [broken](runtimeverification/k#3728) backend update job. When using the new [inlined version of `llvm-kompile`](#814), we were incorrectly using the result of `sys::getDefaultTargetTriple()` as our target for machine code emission, rather than the consistent value selected by running Clang on an empty input file. On newer versions of macOS, this produces warnings like: ``` ld: warning: object file (tmp.1YutNb2k5B.o) was built for newer macOS version (14.0) than being linked (10.12) ``` when running `llvm-kompile`. These warnings were silently absorbed by CI as they are just warnings, but they are a) noisy and b) break the K test suite when grepping for error messages in failed compilations (`kompile ... 2>&1 | grep ...`). The fix is just to use our existing technique for target triple selection in the one place we weren't previously. Additionally, the PR makes two small related changes: * Add conditional compilation guards for some LLVM headers that give deprecation warnings in LLVM 17 * Catch future errors of this kind in the backend CI by ensuring that `llvm-kompile` is silent and doesn't pollute `stderr` with extra output when it runs successfully
…meverification/llvm-backend
…f32204620f90d58a254b65fc37
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.
No description provided.