summaryrefslogtreecommitdiffstats
path: root/lld/test/ELF/format-binary-non-ascii.s
Commit message (Collapse)AuthorAgeFilesLines
* [test] Change llvm-readobj -long-option to --long-option or well-known short ↵Fangrui Song2019-05-011-1/+1
| | | | | | | | | | | | 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
* [tests] Fix format-binary-non-ascii.s to work with Python 3 on WindowsAaron Smith2018-04-071-3/+3
| | | | | | | | | | | Some platforms interpret the pound sign as one character. Platforms that use Python 2.x actually interpret it as two characters because in the Python 2.x version of lit, the string used for the file name is a byte string and the pound sign is two bytes. Patch by Stella Stamenova! llvm-svn: 329472
* Replace CRLF.Rui Ueyama2017-09-071-15/+15
| | | | llvm-svn: 312765
* [ELF] Prevent crash with binary inputs with non-ascii file namesJames Henderson2017-09-071-0/+15
If using --format=binary with an input file name that has one or more non-ascii characters in, LLD has undefined behaviour (it crashes on my Windows Debug build) when calling isalnum with these non-ascii characters. Instead, of calling std::isalnum, this patch uses an internal version that ignores the locale and checks a specific subset of characters. Reviewers: ruiu Differential Revision: https://reviews.llvm.org/D37331 llvm-svn: 312705
OpenPOWER on IntegriCloud