Charlie Turner 72ba1af89c Stop uppercasing build attribute data. ... The string data for string-valued build attributes were being unconditionally uppercased. There is no mention in the ARM ABI addenda about case conventions, so it's technically implementation defined as to whether the data are capitialised in some way or not. However, there are good reasons not to captialise the data. * It's less work. * Some vendors may legitimately have case-sensitive checks for these attributes which would fail on LLVM generated object files. * There could be locale issues with uppercasing. The original reasons for uppercasing appear to have stemmed from an old codesourcery toolchain behaviour, see http://comments.gmane.org/gmane.comp.compilers.llvm.cvs/87133 This patch makes the object file emitted no longer captialise string data, it encodes as seen in the assembly source. Change-Id: Ibe20dd6e60d2773d57ff72a78470839033aa5538 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@222882 91177308-0d34-0410-b5e6-96231b3b80d8		2014-11-27 12:13:56 +00:00
..
gold	This test requires asserts because of -stats.	2014-11-25 20:56:56 +00:00
llvm-cov
llvm-lit
llvm-mc
llvm-objdump
llvm-profdata
llvm-readobj	Stop uppercasing build attribute data.	2014-11-27 12:13:56 +00:00
llvm-symbolizer
llvm-vtabledump