summaryrefslogtreecommitdiffstats
path: root/llvm/test/MC/MachO/ARM/data-in-code.s
Commit message (Collapse)AuthorAgeFilesLines
* [llvm-readobj] Test --macho-data-in-code option.Davide Italiano2015-08-221-18/+35
| | | | | | | As added bonus this converts an existing test from macho-dump to llvm-readobj. Only 66 to go. llvm-svn: 245791
* Refactor data-in-code annotations.Jim Grosbach2012-05-181-0/+33
Use a dedicated MachO load command to annotate data-in-code regions. This is the same format the linker produces for final executable images, allowing consistency of representation and use of introspection tools for both object and executable files. Data-in-code regions are annotated via ".data_region"/".end_data_region" directive pairs, with an optional region type. data_region_directive := ".data_region" { region_type } region_type := "jt8" | "jt16" | "jt32" | "jta32" end_data_region_directive := ".end_data_region" The previous handling of ARM-style "$d.*" labels was broken and has been removed. Specifically, it didn't handle ARM vs. Thumb mode when marking the end of the section. rdar://11459456 llvm-svn: 157062
OpenPOWER on IntegriCloud