Open
Conversation
Collaborator
Collaborator
|
should this be upstreamed? |
Author
|
Yes, probably. I can open an llvm-project PR with the same code. |
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
3 participants
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.
A recent change to LLVM is causing missing integer type errors on Linux with GCC 12, GCC 15, and probably other versions. This is part of a series of PRs to address that issue.
The root cause is probably the fact that we partially-but-not-completely have our own C standard library separate from the host library, but that's not something that can be avoided.
The #if guards are probably unnecessary; will fix if there's interest in pursuing this.