Skip to content

IRGen: ensure that ObjC sections match on all targets #13225

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 1 commit into from
Dec 4, 2017

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Dec 2, 2017

Adjust the IRGen for ObjC interop to ensure that the section that
metadata is emitted into the correct section for non-MachO targets.
This also adds a more comprehensive test for ensuring that the IRGen can
now be tested on all targets. Since the ObjC interop is now
controllable via the driver, this test does not require that the
objc_interop feature is present as it is a IRGen test.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@compnerd compnerd force-pushed the objc-irgen branch 2 times, most recently from 41d1f56 to f5c4f80 Compare December 3, 2017 21:47
Adjust the IRGen for ObjC interop to ensure that the section that
metadata is emitted into the correct section for non-MachO targets.

This also adds a more comprehensive test for ensuring that the IRGen can
now be tested on all targets.  Since the ObjC interop is now
controllable via the driver, this test does not require that the
objc_interop feature is present as it is a IRGen test.

This is the first step to remove the `REQUIRES: objc_interop` from the
IRGen tests.
@compnerd
Copy link
Member Author

compnerd commented Dec 3, 2017

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit d9ce520 into swiftlang:master Dec 4, 2017
@aschwaighofer
Copy link
Contributor

Potential fix: dfa4b77

@compnerd compnerd deleted the objc-irgen branch December 4, 2017 03:23
@compnerd
Copy link
Member Author

compnerd commented Dec 4, 2017

@aschwaighofer weird, wonder why. Thanks for the fix!

@jrose-apple
Copy link
Contributor

This test breaks for me when I don't build the iOS stdlib. I think it's because the importer is still trying to look things up in the standard library.

@rudkx
Copy link
Contributor

rudkx commented Jan 18, 2018

@compnerd I just hit a failure on this test as a result of having a stale iOS stdlib sitting around. The test should be split up by target output type with each guarded by REQUIRES: OS=....

@compnerd
Copy link
Member Author

@rudkx sure, I can split it up into three different tests. Sorry, still used to the LLVM style of working where just the architecture matters.

@compnerd
Copy link
Member Author

PR14063 splits up the test into three copies. We can discuss whether that is a good idea or not there.

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.

5 participants