summaryrefslogtreecommitdiff
path: root/docs/MSVCCompatibility.rst
diff options
context:
space:
mode:
authorWarren Hunt <whunt@google.com>2014-07-02 21:46:03 +0000
committerWarren Hunt <whunt@google.com>2014-07-02 21:46:03 +0000
commit0d0deddd24991c545f6cc381e921980c9ccdd39f (patch)
treeb564131efbc1935bf4ec3c243660c291870edaee /docs/MSVCCompatibility.rst
parentc181d7157bf97fe6554a0898510066a0193928cc (diff)
downloadclang-0d0deddd24991c545f6cc381e921980c9ccdd39f.tar.gz
Fix Typo in MSVCCompatibility.rst
Also removed a sentance that was no longer relevant. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@212227 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/MSVCCompatibility.rst')
-rw-r--r--docs/MSVCCompatibility.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/MSVCCompatibility.rst b/docs/MSVCCompatibility.rst
index 243dfd2b6c..f430d6755f 100644
--- a/docs/MSVCCompatibility.rst
+++ b/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.