-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Setup code for Clang types in SIL. #33541
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
Merged
varungandhi-apple
merged 10 commits into
swiftlang:master
from
varungandhi-apple:vg-clang-types-in-sil-setup
Aug 28, 2020
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
362a25a
[AST] Support SILFunctionType/SILBlockStorageType in ClangTypeConverter.
varungandhi-apple c890cdd
[AST] Add functionality for computing Clang types for SIL functions.
varungandhi-apple 1807412
[Serialization] Allow different Clang types in deserialization.
varungandhi-apple eaac23f
[NFC] Remove ASTExtInfo::assertIsFunctionType in favor of checkInvari…
varungandhi-apple 8da4d53
[NFC] Use ClangTypeInfo's implicit null state instead of an extra Opt…
varungandhi-apple eead4ae
[NFC] Remove unused function parameter.
varungandhi-apple eeec16f
[NFC] Remove redundant ExtInfo parameter for getBridgedFunctionType.
varungandhi-apple fdbcd12
[NFC] Bridge based on SILFunctionLanguage instead of Representation.
varungandhi-apple f86aad9
[NFC] Extract computation of SILExtInfoBuilder bits into new method.
varungandhi-apple c4ad840
[NFC] Reuse SILExtInfoBuilder's main constructor in default constructor.
varungandhi-apple File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assert that diffKind fits inside DifferentiabilityMask?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, should we do this consistently for all the fields? For example,
representation
takes two bits. I imagine we could have aLast = 3
case there (and aLast = 2
case forDifferentiabilityKind
) and then have astatic_assert(std::bit_width(DifferentiabilityKind::Last) == std::bit_width(DifferentiabilityMask))
.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Leaving this open for discussion. Will fix this in a follow-up PR based on what you think about the question ^.)