{"push_id":1098698582,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b60d570d6a09e6553ff3f461bc85ad6a4f5d1ca8","before":"74387ad9f0476b9c583e93440681a2ce92644832","commits":[{"sha":"b60d570d6a09e6553ff3f461bc85ad6a4f5d1ca8","author":{"email":"2abc5bb9a8875ba283e7f41f8d9c39ae64fbdadd@apple.com","name":"Kevin Enderby"},"message":"Clean up the specific error message for a malformed Mach-O files with bad segment\nload commands.\n\nThe existing test case in test/Object/macho-invalid.test for\nmacho-invalid-too-small-segment-load-command has a cmdsize of 55, while\nbeing too small also it is not a multiple of 4.  So when that check is added\nthis test case will produce a different error. So I constructed a new test case\nthat will trigger the intended error.\n\nI also changed the error message to be consistent with the other malformed Mach-O\nfile error messages which prints the load command index.  I also removed both\nobject_error::macho_load_segment_too_small and\nobject_error::macho_load_segment_too_many_sections from Object/Error.h\nas they are not needed and can just use object_error::parse_failed and let the\nerror message string distinguish the specific error.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/b60d570d6a09e6553ff3f461bc85ad6a4f5d1ca8"}]}