mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-07-22 09:29:31 +00:00
72ba1af89c
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
18 lines
561 B
ArmAsm
18 lines
561 B
ArmAsm
@ RUN: llvm-mc -triple armv7-eabi -filetype obj -o - %s \
|
|
@ RUN: | llvm-readobj -arm-attributes | FileCheck %s -check-prefix CHECK-ATTR
|
|
|
|
.syntax unified
|
|
.thumb
|
|
@ FIXME: The next directive is not correct, Tag_compatibility isn't getting parsed correctly.
|
|
.eabi_attribute Tag_compatibility, 1
|
|
.eabi_attribute Tag_compatibility, 1, "aeabi"
|
|
|
|
@ CHECK-ATTR: FileAttributes {
|
|
@ CHECK-ATTR: Attribute {
|
|
@ CHECK-ATTR: Value: 1, aeabi
|
|
@ CHECK-ATTR: TagName: compatibility
|
|
@ CHECK-ATTR: Description: AEABI Conformant
|
|
@ CHECK-ATTR: }
|
|
@ CHECK-ATTR: }
|
|
|