Skip to content

[IRGen] Reject enums with inaccessible tpye metadata in layout string… #65016

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
merged 4 commits into from
Apr 14, 2023

Conversation

drexin
Copy link
Contributor

@drexin drexin commented Apr 7, 2023

… generation

rdar://107679697

Because we are currently handling most enums in layout strings by going through the metadata, we have to ensure that the metadata is accessible from the current module and reject the enum otherwise.

… generation

rdar://107679697

Because we are currently handling most enums in layout strings by going through the metadata, we have to ensure that the metadata is accessible from the current module and reject the enum otherwise.
@drexin
Copy link
Contributor Author

drexin commented Apr 7, 2023

@swift-ci smoke test

@drexin
Copy link
Contributor Author

drexin commented Apr 8, 2023

@swift-ci smoke test

@drexin
Copy link
Contributor Author

drexin commented Apr 13, 2023

@swift-ci smoke test

@drexin
Copy link
Contributor Author

drexin commented Apr 13, 2023

@swift-ci smoke test

@drexin drexin merged commit 883750e into swiftlang:main Apr 14, 2023
@drexin drexin deleted the wip-107679697 branch April 14, 2023 05:16
meg-gupta pushed a commit to meg-gupta/swift that referenced this pull request Apr 14, 2023
swiftlang#65016)

* [IRGen] Reject enums with inaccessible tpye metadata in layout string generation

rdar://107679697

Because we are currently handling most enums in layout strings by going through the metadata, we have to ensure that the metadata is accessible from the current module and reject the enum otherwise.

* Use proper mechanism to create and reference dylib in test

* Fix linking

* Add rpath to test dylib
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants