Skip to content

[ClangImporter] Don't pass API notes options when compiling bitcode. #10425

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

Conversation

jrose-apple
Copy link
Contributor

  • Explanation: We were setting up our embedded Clang context with API notes options even when trying to compile bitcode. This resulted in an "argument unused" warning, since these options have no effect on bitcode compilation. Stop doing that. (-embed-bitcode compiles in two steps: source -> bitcode, then bitcode -> object file. This is about the second step.)
  • Scope: Affects builds with -embed-bitcode turned on.
  • Radar: rdar://problem/31372950
  • Reviewed by: me (patch by @bob-wilson)
  • Risk: Very low. These arguments would have been ignored anyway.
  • Testing: Added compiler regression test.

…wiftlang#10422)

Avoids a bogus "argument unused" warning, since bitcode compilation
doesn't bother to set up much of a Clang AST context. (-embed-bitcode
compiles in two steps: source -> bitcode, then bitcode -> object
file. This is about the second step.)

Patch by Bob Wilson, who's currently on vacation but wanted this to
get in sooner rather than later.

rdar://problem/31372950
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

@jrose-apple jrose-apple merged commit ec2d5bc into swiftlang:swift-4.0-branch Jun 21, 2017
@jrose-apple jrose-apple deleted the 4.0-embed-bitcode-more-quietly branch June 21, 2017 00:21
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.

1 participant