Fix some typos

llvm-svn: 207994

clang/include/clang/AST/Type.h

@@ -4223,7 +4223,7 @@ class PackExpansionType : public Type, public llvm::FoldingSetNode {
                     Optional<unsigned> NumExpansions)
     : Type(PackExpansion, Canon, /*Dependent=*/Pattern->isDependentType(),
            /*InstantiationDependent=*/true,
-           /*VariableModified=*/Pattern->isVariablyModifiedType(),
+           /*VariablyModified=*/Pattern->isVariablyModifiedType(),
            /*ContainsUnexpandedParameterPack=*/false),
       Pattern(Pattern),
       NumExpansions(NumExpansions? *NumExpansions + 1: 0) { }

clang/lib/AST/RecordLayoutBuilder.cpp

@@ -2110,7 +2110,7 @@ static bool isMsLayout(const RecordDecl* D) {
 //   when used as a field or base, will not be aligned if #pragma pack is
 //   still active at the time of use.
 //
-// Known incompatiblities:
+// Known incompatibilities:
 // * all: #pragma pack between fields in a record
 // * 2010 and back: If the last field in a record is a bitfield, every object
 //   laid out after the record will have extra padding inserted before it.  The
@@ -2125,7 +2125,7 @@ static bool isMsLayout(const RecordDecl* D) {
 //   _every_ field getting padding put in front of it, potentially including the
 //   vfptr, leaving the vfprt at a non-zero location which results in a fault if
 //   anything tries to read the vftbl.  The second layout phase also treats
-//   bitfields as seperate entities and gives them each storage rather than
+//   bitfields as separate entities and gives them each storage rather than
 //   packing them.  Additionally, because this phase appears to perform a
 //   (an unstable) sort on the members before laying them out and because merged
 //   bitfields have the same address, the bitfields end up in whatever order

clang/test/CodeGen/xcore-stringtype.c

@@ -5,8 +5,8 @@
 
 // In the tests below, some types are not supported by the ABI (_Complex,
 // variable length arrays) and will thus emit no meta data.
-// The 33 tests that do emit typstrings are gathered into '!xcore.typestrings'
-// Please see 'Tools Developement Guide' section 2.16.2 for format details:
+// The 33 tests that do emit typestrings are gathered into '!xcore.typestrings'
+// Please see 'Tools Development Guide' section 2.16.2 for format details:
 // <https://www.xmos.com/download/public/Tools-Development-Guide%28X9114A%29.pdf>
 
 // CHECK: !xcore.typestrings = !{!0, !1, !2, !3, !4, !5, !6, !7, !8, !9, !10,

clang/test/Sema/warn-unreachable.c

@@ -202,7 +202,7 @@ void trivial_dead_return_void() {
   return; // expected-warning {{'return' will never be executed}}
 }
 
-MyEnum trival_dead_return_enum() {
+MyEnum trivial_dead_return_enum() {
   raze();
   return Value1; // expected-warning {{'return' will never be executed}}
 }
@@ -333,7 +333,7 @@ void trivial_dead_return_void_SUPPRESSED() {
   return; // no-warning
 }
 
-MyEnum trival_dead_return_enum_SUPPRESSED() {
+MyEnum trivial_dead_return_enum_SUPPRESSED() {
   raze();
   return Value1; // no-warning
 }