Skip to content

build: bump C++ standard to 14 #112

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
Sep 8, 2020

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Sep 7, 2020

The Windows C++ runtime requires C++14. This is handled transparently
when using the clang-cl driver, however, when building with s-p-m, the
clang driver is used instead. This requires explicitly bumping
everything to C++14.

The Windows C++ runtime requires C++14.  This is handled transparently
when using the `clang-cl` driver, however, when building with s-p-m, the
`clang` driver is used instead.  This requires explicitly bumping
everything to C++14.
@compnerd
Copy link
Member Author

compnerd commented Sep 7, 2020

@akyrtzi @benlangmuir - I'm not sure if this is acceptable or not. I couldn't figure out a way to do a build condition on the setting here, which would be another option otherwise. But, the current MSVC C++ STL headers use C++14 features unconditionally.

Copy link
Contributor

@benlangmuir benlangmuir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the tests pass, it's fine with me. We would need to change this anyway on all platforms next time we update our llvm support code (it's currently from April 2019, which was a few months before c++14 became mandatory in llvm).

@benlangmuir
Copy link
Contributor

@swift-ci please test

@benlangmuir benlangmuir merged commit c2d6f20 into swiftlang:master Sep 8, 2020
@compnerd compnerd deleted the cxx-standard branch September 8, 2020 20:49
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