summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/note-contiguous.s
Commit message (Collapse)AuthorAgeFilesLines
* [test] Change llvm-readobj -long-option to --long-option or well-known short ↵Fangrui Song2019-05-011-2/+2
| | | | | | | | | | | | options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
* Do not create multiple NOTE segments.Rui Ueyama2018-03-011-2/+4
| | | | | | | | | | | Previously, we didn't try to make effort to put .note sections next to each other in the output file, so two .note sections were likely to be stored to two separate NOTE segments. That's undesirable because we should create as few segments as possible in general. Differential Revision: https://reviews.llvm.org/D43858 llvm-svn: 326410
* Expand test a bit.Rafael Espindola2018-03-011-11/+27
| | | | | | | | | It now includes both linkerscript and non linkerscript variants. Extracted from a patch by Rui while I was trying to figure out what exactly was changing. llvm-svn: 326409
* [ELF] Handle multiple discontiguous .note sectionsPetr Hosek2017-02-011-0/+24
There could be multiple discontiguous output .note sections in which case we need to put these into separate PT_NOTE segments rather then placing them into a single segment. Where possible, we could reorder the input sections to make sure that all .note are layed out next to each other to avoid creation multiple PT_NOTE segments, but even in that case, it's still possible to construct a discontiguous case e.g. by using a linker script. Differential Revision: https://reviews.llvm.org/D29364 llvm-svn: 293811
OpenPOWER on IntegriCloud