diff options
| -rw-r--r-- | clang/docs/MSVCCompatibility.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/clang/docs/MSVCCompatibility.rst b/clang/docs/MSVCCompatibility.rst index 243dfd2b6c3..f430d6755f0 100644 --- a/clang/docs/MSVCCompatibility.rst +++ b/clang/docs/MSVCCompatibility.rst @@ -19,7 +19,7 @@ MSVC. There are multiple dimensions to compatibility. First, Clang attempts to be ABI-compatible, meaning that Clang-compiled code should be able to link against MSVC-compiled code successfully. However, C++ -ABIs are particular large and complicated, and Clang's support for MSVC's C++ +ABIs are particularly large and complicated, and Clang's support for MSVC's C++ ABI is a work in progress. If you don't require MSVC ABI compatibility or don't want to use Microsoft's C and C++ runtimes, the mingw32 toolchain might be a better fit for your project. @@ -82,7 +82,7 @@ The status of major ABI-impacting C++ features: finished, along with support for the ``/GR`` flag. * Exceptions and SEH: :none:`Unstarted`. Clang can parse both constructs, but - does not know how to emit compatible handlers. This depends on RTTI. + does not know how to emit compatible handlers. * Thread-safe initialization of local statics: :none:`Unstarted`. We are ABI compatible with MSVC 2013, which does not support thread-safe local statics. |
