Modernize use of LLVM pointer types #639
Merged
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
|
Ok, I think that's all the easy cases. Everything else either (a) becomes superfluous once pointer types are removed (i.e., there will be no more bitcasts, so it doesn't matter what we bitcast to), or (b) is more challenging (i.e., I need to figure out how to get types safely out of Clang without them being pruned). |
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.
This is the first part of the migration toward opaque pointers (#553). Starting with the easy cases, I'm trying to reduce the compiler's reliance on looking up pointee types. But this PR may not get 100% of all the cases.