[JITLink] Remove CodeAlignmentFactor and DataAlignmentFactor validation

[sunho]

Summary

This patch removes CodeAlignmentFactor and DataAlignmentFactor validation in EHFrameEdgeFixer. I observed some of aarch64 elf files generated by clang contains CIE record with code_alignment_factor = 4 or data_alignment_factor = -8. If I'm understading correctly, code_alignment_factor and data_alignment_factor are used by call fram instruction that should be correctled handled by libunwind. But, I also see the verification was added in the intial code base and not touched since then.

[lhames]

LGTM. Thanks @sunho!

llvm/lib/ExecutionEngine/JITLink/EHFrameSupport.cpp

if (AugInfo->EHDataFieldPresent)
     if (auto Err = RecordReader.skip(PC.G.getPointerSize()))
       return Err;
 
   // Read and validate the code alignment factor.
   {
     uint64_t CodeAlignmentFactor = 0;
     if (auto Err = RecordReader.readULEB128(CodeAlignmentFactor))
       return Err;
-    if (CodeAlignmentFactor != 1)
-      return make_error<JITLinkError>("Unsupported CIE code alignment factor " +
-                                      Twine(CodeAlignmentFactor) +
-                                      " (expected 1)");
   }
 
   // Read and validate the data alignment factor.
   {
     int64_t DataAlignmentFactor = 0;
     if (auto Err = RecordReader.readSLEB128(DataAlignmentFactor))
       return Err;
-    if (DataAlignmentFactor != -8)
-      return make_error<JITLinkError>("Unsupported CIE data alignment factor " +
-                                      Twine(DataAlignmentFactor) +
-                                      " (expected -8)");
   }
 
   // Skip the return address register field.
   if (auto Err = RecordReader.skip(1))
     return Err;
 
   if (AugInfo->AugmentationDataPresent) {