
LLVM has started to emit AArch64 build attributes sections called .ARM.attributes. LLD does not yet have support for these so they are accumulating in the ELF output. As the first part of that support discard all the .ARM.attributes sections. This can be built upon by the full implementation in LLD. The build attributes specification only defines build attributes for relocatable objects. The intention for LLD is that files of type ET_EXEC and ET_SHARED will not have a build attributes in the output. A relocatable link with -r will need a merged build attributes, but until the merge is implemented it is better to discard.
27 lines
895 B
ArmAsm
27 lines
895 B
ArmAsm
// REQUIRES: aarch64
|
|
// RUN: llvm-mc -triple=aarch64 %s -filetype=obj -o %t.o
|
|
// RUN: ld.lld %t.o --shared -o %t.so
|
|
// RUN: llvm-readelf --sections %t.so | FileCheck %s
|
|
// RUN: ld.lld %t.o -o %t
|
|
// RUN: llvm-readelf --sections %t | FileCheck %s
|
|
// RUN: ld.lld -r %t.o -o %t2.o
|
|
// RUN: llvm-readelf --sections %t2.o | FileCheck %s
|
|
|
|
/// File has a Build attributes section. This should not appear in
|
|
/// ET_EXEC or ET_SHARED files as there is no requirement for it to
|
|
/// do so. FIXME, the ld -r (relocatable link) should output a single
|
|
/// merged build attributes section. When full support is added in
|
|
/// ld.lld this test should be updated.
|
|
|
|
// CHECK-NOT: .ARM.attributes
|
|
|
|
.aeabi_subsection aeabi_feature_and_bits, optional, uleb128
|
|
.aeabi_attribute Tag_Feature_BTI, 1
|
|
.aeabi_attribute Tag_Feature_PAC, 1
|
|
.aeabi_attribute Tag_Feature_GCS, 1
|
|
|
|
.global _start
|
|
.type _start, %function
|
|
_start:
|
|
ret
|