aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/ObjectYAML/MachOYAML.cpp
AgeCommit message (Collapse)AuthorFilesLines
2019-08-20[yaml2obj/obj2yaml][MachO] Allow setting custom section dataSeiya Nuta1-0/+9
Reviewers: alexshap, jhenderson, rupprecht Reviewed By: alexshap, jhenderson Subscribers: abrachet, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D65799 llvm-svn: 369348
2019-01-19Update the file headers across all of the LLVM projects in the monorepoChandler Carruth1-4/+3
to reflect the new license. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351636
2017-12-18[YAML] Add support for non-printable charactersFrancis Visoiu Mistrih1-2/+6
LLVM IR function names which disable mangling start with '\01' (https://www.llvm.org/docs/LangRef.html#identifiers). When an identifier like "\01@abc@" gets dumped to MIR, it is quoted, but only with single quotes. http://www.yaml.org/spec/1.2/spec.html#id2770814: "The allowed character range explicitly excludes the C0 control block allowed), the surrogate block #xD800-#xDFFF, #xFFFE, and #xFFFF." http://www.yaml.org/spec/1.2/spec.html#id2776092: "All non-printable characters must be escaped. [...] Note that escape sequences are only interpreted in double-quoted scalars." This patch adds support for printing escaped non-printable characters between double quotes if needed. Should also fix PR31743. Differential Revision: https://reviews.llvm.org/D41290 llvm-svn: 320996
2017-09-13llvm-dwarfdump: support dumping UUIDs of Mach-O binaries.Adrian Prantl1-5/+1
This is a feature supported by Darwin dwarfdump. UUIDs are used to associate executables with their .dSYM bundles. llvm-svn: 313165
2017-07-01[ObjectYAML] Fix some Clang-tidy modernize and Include What You Use ↵Eugene Zelenko1-38/+12
warnings; other minor fixes (NFC). llvm-svn: 306925
2017-06-07Move Object format code to lib/BinaryFormat.Zachary Turner1-2/+2
This creates a new library called BinaryFormat that has all of the headers from llvm/Support containing structure and layout definitions for various types of binary formats like dwarf, coff, elf, etc as well as the code for identifying a file from its magic. Differential Revision: https://reviews.llvm.org/D33843 llvm-svn: 304864
2017-01-23Add LC_BUILD_VERSION load commandSteven Wu1-0/+21
Summary: Add a new load command LC_BUILD_VERSION. It is a generic version of LC_*_VERSION_MIN load_command used on Apple platforms. Instead of having a seperate load command for each platform, LC_BUILD_VERSION is recording platform info as an enum. It also records SDK version, min_os, and tools that used to build the binary. rdar://problem/29781291 Reviewers: enderby Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D29044 llvm-svn: 292824
2017-01-19Add support for the new LC_NOTE load command.Kevin Enderby1-0/+8
It describes a region of arbitrary data included in a Mach-O file. Its initial use is to record extra data in MH_CORE files. rdar://30001545 rdar://30001731 llvm-svn: 292500
2016-12-22[ObjectYAML] MachO support for endiannessChris Bieneman1-0/+5
This patch adds support to the macho<->yaml tools for preserving endianness in MachO structures and DWARF data. llvm-svn: 290381
2016-12-07[ObjectYAML] Pull DWARF support into DWARFYAML namespaceChris Bieneman1-24/+0
Since DWARF formatting is agnostic to the object file it is stored in, it doesn't make sense for this to be in the MachOYAML implementation. Pulling it into its own namespace means we could modify the ELF and COFF YAML tools to emit DWARF as well. In a follow-up patch I will better abstract this in obj2yaml and yaml2obj so that the DWARF bits in the tools can be re-used too. llvm-svn: 288984
2016-12-07[ObjectYAML] Rename DWARF entries to match section namesChris Bieneman1-2/+2
This change makes the yaml tags for the members of the DWARF data match the names of the DWARF sections. llvm-svn: 288981
2016-12-07[ObjectYAML] Support for DWARF __debug_abbrev sectionChris Bieneman1-2/+17
This patch adds support for round-tripping DWARF debug abbreviations through the obj<->yaml tools. llvm-svn: 288955
2016-12-06[ObjectYAML] First bit of support for encoding DWARF in MachOChris Bieneman1-1/+16
This patch adds the starting support for encoding data from the MachO __DWARF segment. The first section supported is the __debug_str section because it is the simplest. llvm-svn: 288774
2016-08-17[macho2yaml] Don't write empty linkedit dataChris Bieneman1-1/+6
Since I stopped writing empty export tries it causes LinkEdit to potentially be completely empty which results in invalid yaml being generated. To prevent this we skip linkedit data if it is empty. llvm-svn: 278985
2016-08-11[MachOYAML] Don't output empty ExportTrieChris Bieneman1-1/+2
The YAML representation was always outputting the root node of an export trie even if the trie was empty. While this doesn't really have any functional impact, it does add visual clutter to the yaml file. llvm-svn: 278307
2016-06-28[YAML] Fix YAML tags appearing before the start of sequence elementsChris Bieneman1-1/+1
Our existing yaml::Output code writes tags immediately when mapTag is called, without any state handling. This results in tags on sequence elements being written before the element itself. For example, we see this: SomeArray: !elem_type - key1: 1 key2: 2 !elem_type2 - key3: 3 key4: 4 We should instead see: SomeArray: - !elem_type key1: 1 key2: 2 - !elem_type2 key3: 3 key4: 4 Our reader handles reading properly, so this bug only impacts writing yaml sequences with tagged elements. As a test for this I've modified the Mach-O yaml encoding to allways apply the !mach-o tag when encoding MachOYAML::Object entries. This results in the !mach-o tag appearing as expected in dumped fat files. llvm-svn: 274067
2016-06-27[yaml2obj] Remove --format option in favor of YAML tagsChris Bieneman1-28/+0
Summary: Our YAML library's handling of tags isn't perfect, but it is good enough to get rid of the need for the --format argument to yaml2obj. This patch does exactly that. Instead of requiring --format, it infers the format based on the tags found in the object file. The supported tags are: !ELF !COFF !mach-o !fat-mach-o I have a corresponding patch that is quite large that fixes up all the in-tree test cases. Reviewers: rafael, Bigcheese, compnerd, silvas Subscribers: compnerd, llvm-commits Differential Revision: http://reviews.llvm.org/D21711 llvm-svn: 273915
2016-06-24[obj2yaml] [yaml2obj] Support for MachO Universal binariesChris Bieneman1-1/+62
This patch adds round-trip support for MachO Universal binaries to obj2yaml and yaml2obj. Universal binaries have a header and list of architecture structures, followed by a the individual object files at specified offsets. llvm-svn: 273719
2016-06-23[MachOYAML] Use a temporary to avoid gcc strict-aliasing warningChris Bieneman1-2/+4
GCC complains about this with -Wstrict-aliasing. Using a temporary here should prevent the warning. llvm-svn: 273627
2016-06-23[yaml2macho] Removing asserts in favor of explicit yaml parse errorChris Bieneman1-2/+4
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
2016-06-02[obj2yaml] [yaml2obj] Support for MachO nlist and string tableChris Bieneman1-0/+11
This commit adds round tripping for MachO symbol data. Symbols are entries in the name list, that contain offsets into the string table which is at the end of the __LINKEDIT segment. llvm-svn: 271604
2016-05-31[obj2yaml][yaml2obj] Support for reading and dumping the MachO export trieChris Bieneman1-0/+19
The MachO export trie is a serially encoded trie keyed by symbol name. This code parses the trie and preserves the structure so that it can be dumped again. llvm-svn: 271300
2016-05-26[obj2yaml][yaml2obj] Support for MachO lazy bindingsChris Bieneman1-0/+1
This adds support for YAML round tripping dyld info lazy bindings. The storage and format of these is the same as regular bind opcodes, they are just interpreted differently by dyld, and can have DONE opcodes in the middle of the opcode lists. llvm-svn: 270920
2016-05-26[obj2yaml][yaml2obj] Support for MachO weak bindingsChris Bieneman1-0/+1
This adds support for YAML round tripping dyld info weak bindings. The storage and format of these is the same as regular bind opcodes, they are just interpreted differently by dyld. llvm-svn: 270911
2016-05-26[obj2yaml][yaml2obj] Support for MachO bind opcodesChris Bieneman1-4/+14
This adds support for YAML round tripping dyld info bind opcodes. Bind opcodes can have signed or unsigned LEB128 data, and they can have symbols associated with them. llvm-svn: 270901
2016-05-25[obj2yaml] [yaml2obj] MachO support for rebase opcodesChris Bieneman1-0/+13
This is the first bit of support for MachO __LINKEDIT segment data. llvm-svn: 270724
2016-05-20[MachOYAML] Removing duplicated field from LC_UUID YAMLChris Bieneman1-1/+0
The uuid_command was duplicating the load_command.cmdsize field. This removes the duplicate from the YAML mapping and from the test cases. llvm-svn: 270248
2016-05-19[obj2yaml] [yaml2obj] Support for MachO Load Command dataChris Bieneman1-4/+30
This re-applies r270115. Many of the MachO load commands can have data appended after the command structure. This data is frequently strings, but can actually be anything. This patch adds support for three optional fields on load command yaml descriptions. The new PayloadString YAML field is populated with the data after load commands known to have strings as extra data. The new ZeroPadBytes YAML field is a count of zero'd bytes after the end of the load command structure before the next command. This can apply anywhere in the file. MachO2YAML verifies that bytes are zero before populating this field, and YAML2MachO will add zero'd bytes. The new PayloadBytes YAML field stores all bytes after the end of the load command structure before the next command if they are non-zero. This is a catch all for all unhandled bytes. If MachO2Yaml populates PayloadBytes it will not populate ZeroPadBytes, instead zero'd bytes will be in the PayloadBytes structure. llvm-svn: 270124
2016-05-19Revert "[obj2yaml] [yaml2obj] Support for MachO Load Command data"Chris Bieneman1-30/+4
This reverts commit r270115. This failed on several builders using GCC. llvm-svn: 270121
2016-05-19[obj2yaml] [yaml2obj] Support for MachO Load Command dataChris Bieneman1-4/+30
Many of the MachO load commands can have data appended after the command structure. This data is frequently strings, but can actually be anything. This patch adds support for three optional fields on load command yaml descriptions. The new PayloadString YAML field is populated with the data after load commands known to have strings as extra data. The new ZeroPadBytes YAML field is a count of zero'd bytes after the end of the load command structure before the next command. This can apply anywhere in the file. MachO2YAML verifies that bytes are zero before populating this field, and YAML2MachO will add zero'd bytes. The new PayloadBytes YAML field stores all bytes after the end of the load command structure before the next command if they are non-zero. This is a catch all for all unhandled bytes. If MachO2Yaml populates PayloadBytes it will not populate ZeroPadBytes, instead zero'd bytes will be in the PayloadBytes structure. llvm-svn: 270115
2016-05-18Re-apply: [obj2yaml] [yaml2obj] Support MachO section and section_64Chris Bieneman1-4/+27
This re-applies r269845, r269846, and r269850 with an included fix for a crash reported by zturner. llvm-svn: 269953
2016-05-17Revert "[obj2yaml] [yaml2obj] Support MachO section and section_64Zachary Turner1-24/+2
structs" This reverts commits r269845, r269846, and r269850 as they introduce a crash in obj2yaml when trying to do a roundtrip. llvm-svn: 269865
2016-05-17[obj2yaml][yaml2obj] Fixing dyld_info_command mappingsChris Bieneman1-2/+4
Apparently I mucked up the mappings here, which was causing some binary differences in round tripping. llvm-svn: 269846
2016-05-17[obj2yaml] [yaml2obj] Support MachO section and section_64 structsChris Bieneman1-0/+20
This patch adds round trip support for MachO section structs. llvm-svn: 269845
2016-05-17Reapply r269782 "[obj2yaml] [yaml2obj] Support for MachO load command ↵Chris Bieneman1-6/+353
structures"" This adds support for all the MachO *_command structures. The load_command payloads still are not represented, but that will come next. llvm-svn: 269808
2016-05-17Revert "[obj2yaml] [yaml2obj] Support for MachO load command structures"Chris Bieneman1-354/+6
This reverts commit r269782 because it broke bots with -fpermissive. llvm-svn: 269785
2016-05-17[obj2yaml] [yaml2obj] Support for MachO load command structuresChris Bieneman1-6/+354
This adds support for all the MachO *_command structures. The load_command payloads still are not represented, but that will come next. llvm-svn: 269782
2016-05-13[obj2yaml] [yaml2obj] Basic support for MachO::load_commandChris Bieneman1-0/+11
This patch adds basic support for MachO::load_command. Load command types and sizes are encoded in the YAML and expanded back into MachO. The YAML doesn't yet support load command structs, that is coming next. In the meantime as a temporary measure when writing MachO files the load commands are padded with zeros so that the generated binary is valid. llvm-svn: 269442
2016-05-12[yaml2macho] Handle mach_header_64 reserved fieldChris Bieneman1-0/+2
I've added the reserved field as an "optional" in YAML, but I've added asserts in the yaml2macho code to enforce that the field is present in mach_header_64, but not in mach_header. llvm-svn: 269320
2016-05-12[ObjectYAML] filetype is a required field in MachO headersChris Bieneman1-1/+1
Not sure how I managed to copy-pasta this wrong, but I did. llvm-svn: 269317
2016-05-12[obj2yaml] Include all mach_header fields in yamlChris Bieneman1-1/+3
Since we want to be able to use yaml to describe degenerate object files as well as valid ones, we need to be explicit of some fields in your yaml definitions. llvm-svn: 269313
2016-05-12[ObjectYAML] Support Thin MachO headers to YAMLChris Bieneman1-0/+44
This patch adds support to ObjectYAML for serializing mach_header structs. llvm-svn: 269303
generated by cgit v1.1 at 2025-10-08 20:28:01 +0000