{"push_id":2769086704,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"58b1de483d3252d62213d434b01b859ed34d060d","before":"f4a5ef1f003caf18cf27d47d17cd4b0746e6bd51","commits":[{"sha":"58b1de483d3252d62213d434b01b859ed34d060d","author":{"name":"Dave Lee","email":"7fc782f5ff4030ed0927a18d5be1abaf2d90571c@gmail.com"},"message":"objdump: Better handling of Mach-O universal binaries\n\nSummary:\nWith Mach-O, there is a flag requirement discrepancy between working with\nuniversal binaries and thin binaries. Many flags that don't require the `-macho`\nflag (for example `-private-headers` and `-disassemble`) fail to work on\nuniversal binaries unless `-macho` is given. When this happens, the error\nmessage is unhelpful, stating:\n\n    The file was not recognized as a valid object file.\n\nWhich can lead to confusion.\n\nThis change allows generic flags to be used on universal binaries with and\nwithout the `-macho` flag. This means flags that can be used for thin files can\nbe used consistently with fat files too.\n\nTo do this, the universal binary support within `ParseInputMachO()` is extracted\ninto a new function. This new function is called directly from `DumpInput()`\nwhen the input binary is universal. Additionally the `-arch` flag validation in\n`ParseInputMachO()` was extracted to be reused.\n\nReviewers: compnerd\n\nReviewed By: compnerd\n\nSubscribers: keith, llvm-commits\n\nDifferential Revision: https://reviews.llvm.org/D48702\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@338792 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-mirror/llvm/commits/58b1de483d3252d62213d434b01b859ed34d060d"}]}
{"actor":{"display_login":"dtzWill"}}