aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitstreamReader.cpp
diff options
context:
space:
mode:
authorKevin Enderby <enderby@apple.com>2016-10-27 20:59:10 +0000
committerKevin Enderby <enderby@apple.com>2016-10-27 20:59:10 +0000
commitbc5c29a65f5326484b12384a519945df341aa557 (patch)
tree6cd051b43e595fa7c67011d9bd556411a0f5d55f /llvm/lib/Bitcode/Reader/BitstreamReader.cpp
parent58e14743cae66da3a19bed8e95f2c6a118263933 (diff)
downloadllvm-bc5c29a65f5326484b12384a519945df341aa557.zip
llvm-bc5c29a65f5326484b12384a519945df341aa557.tar.gz
llvm-bc5c29a65f5326484b12384a519945df341aa557.tar.bz2
Another additional error check for invalid Mach-O files for the
obsolete load commands. Again the philosophy of the error checking in libObject for Mach-O files, the idea behind the checking is that we never will return a Mach-O file out of libObject that contains unknown things the library code can’t operate on. So known obsolete load commands will cause a hard error. Also to make things clear I have added comments to the values and structures in Support/Mach-O.h and Support/MachO.def as to what is obsolete. As noted in a TODO in the code, there may need to be a non-default mode to allow some unknown values for well structured Mach-O files with things like unknown load load commands. So things like using an old lldb on a newer Mach-O file could still provide some limited functionality. llvm-svn: 285342
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitstreamReader.cpp')
0 files changed, 0 insertions, 0 deletions