maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/ARM/directive-eabi_attribute-ov...

16 lines
429 B
ArmAsm
Raw Normal View History

ARM: change attribute tests to use parsed form This makes the tests more readable by using the -arm-attributes decoding support in llvm-readobj since that is now available. Change the invocation commands to be similar to other test and use a more precise triple (the tests only require ARM EABI support). llvm-svn: 201029
2014-02-09 07:17:02 +08:00
@ RUN: llvm-mc -triple armv7-eabi -filetype obj -o - %s \
@ RUN: | llvm-readobj -arm-attributes | FileCheck %s -check-prefix CHECK-ATTR
ARM ELF: ensure that the tag types are corrected Ensure that the tag types are reflected on a replacement. This is particularly important for the compatibility tag which has multiple representations where the last definition wins. llvm-svn: 199577
2014-01-19 16:25:41 +08:00
.syntax unified
.thumb
.eabi_attribute Tag_compatibility, 1, "aeabi"
ARM: change attribute tests to use parsed form This makes the tests more readable by using the -arm-attributes decoding support in llvm-readobj since that is now available. Change the invocation commands to be similar to other test and use a more precise triple (the tests only require ARM EABI support). llvm-svn: 201029
2014-02-09 07:17:02 +08:00
@ CHECK-ATTR: FileAttributes {
@ CHECK-ATTR: Attribute {
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 llvm-svn: 222882
2014-11-27 20:13:56 +08:00
@ CHECK-ATTR: Value: 1, aeabi
ARM: change attribute tests to use parsed form This makes the tests more readable by using the -arm-attributes decoding support in llvm-readobj since that is now available. Change the invocation commands to be similar to other test and use a more precise triple (the tests only require ARM EABI support). llvm-svn: 201029
2014-02-09 07:17:02 +08:00
@ CHECK-ATTR: TagName: compatibility
@ CHECK-ATTR: Description: AEABI Conformant
@ CHECK-ATTR: }
@ CHECK-ATTR: }
ARM ELF: ensure that the tag types are corrected Ensure that the tag types are reflected on a replacement. This is particularly important for the compatibility tag which has multiple representations where the last definition wins. llvm-svn: 199577
2014-01-19 16:25:41 +08:00