[yaml2macho] Removing asserts in favor of explicit yaml parse error

32-bit Mach headers don't have reserved fields. When generating the
mapping for 32-bit headers leaving off the reserved field will result in
parse errors if the field is present in the yaml.

Added a CHECK-NOT line to ensure that mach_header.yaml isn't adding a
reserved field, and a test to ensure that the parser error gets hit with
32-bit headers.

llvm-svn: 273623

1 files changed, 0 insertions, 4 deletions

diff --git a/llvm/tools/yaml2obj/yaml2macho.cpp b/llvm/tools/yaml2obj/yaml2macho.cpp
index 510f7609b75..7821e63cf88 100644
--- a/llvm/tools/yaml2obj/yaml2macho.cpp
+++ b/llvm/tools/yaml2obj/yaml2macho.cpp
@@ -32,10 +32,6 @@ public:
     is64Bit = Obj.Header.magic == MachO::MH_MAGIC_64 ||
               Obj.Header.magic == MachO::MH_CIGAM_64;
     memset(reinterpret_cast<void *>(&Header), 0, sizeof(MachO::mach_header_64));
-    assert((is64Bit || Obj.Header.reserved == 0xDEADBEEFu) &&
-           "32-bit MachO has reserved in header");
-    assert((!is64Bit || Obj.Header.reserved != 0xDEADBEEFu) &&
-           "64-bit MachO has missing reserved in header");
   }
 
   Error writeMachO(raw_ostream &OS);