Upgrade libc++ to 7.0

[kaimast]

As far as I understand the SDK officially supports C++11.

There are a bunch of features in the 2014 and 2017 revisions that are fairly useful such as std::optional or std::shared_mutexes.

Are there plans to eventually sync the standard library with a more recent version to support c++14 or even c++17?

[andyzyb]

Currently these is no plan to support C++14/17 in the near future unless we see some strong requests from external users.

[ruizpauker]

I vote up this.

C++17 introduces a lot of simplification to the code, which make the codebase small and more readable as its C++11 counterpart, these are, IMHO key facts that align perfectly to keeping the TCB small as possible.

[AmbitionXiang]

I vote up this, too.

For example, auto addition2 = [](int _1)->auto { return [_1](int _2)->int{ return _1 + _2; }; }; The second auto is correct in C++14, while error in C++11. It's inconvenient to write std::function<int(int)>

[bogdatim]

I also vote up this. Absence of new C++ standard support increases time to market for products based on SGX because you can not take existing libraries written on c++14/17 and adapt them to be used in enclave. Any plans to add c++14/17 support to the SGX SDK trusted libraries in near future?

[0xWilliamWang]

I also vote up this. I want to use seal ,but it written on c++14/17. thanks.

[dnat112]

I see that the latest update included adding c++14 support. Does this update support all features of c++14, or just some subset of them? If the latter, is there a list somewhere of what is/isn't supported?

[jbdelcuv]

Have a look at section "C++14 Support on Linux* OS" in the Appendix of the SGX SDK Developer Reference.