6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-16 11:05:54 +00:00
Code Issues Projects Releases Wiki Activity
29e85bc728
llvm-6502/test/MC/ELF/undef.s

47 lines
1.4 KiB
ArmAsm
Raw Normal View History

On elf, undefined symbols can start with .L. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@114958 91177308-0d34-0410-b5e6-96231b3b80d8
2010-09-28 16:19:11 +00:00
// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | elf-dump | FileCheck %s
Tests that now pass. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@115622 91177308-0d34-0410-b5e6-96231b3b80d8
2010-10-05 15:43:32 +00:00
// Test which symbols should be in the symbol table
.long .Lsym1
.Lsym2:
.Lsym3:
.Lsym4 = .Lsym2 - .Lsym3
.long .Lsym4
.type .Lsym5,@object
.type sym6,@object
Be more strict on when we produce an undefined reference. In gas a file with just .type foo,@object will produce an undefined reference to foo. On the other hand, a file with just .weakref bar, foo will not. It is somewhat hard to support both in MC since both statements should create the symbols. It should be possible if we really need to by adding to the flags, but hopefully that is not necessary. With this patch we do not produce a undefined reference in any of those cases. The assembly file needs an actual use for the undefined reference to be present. This is in preparation for a patch implementing .weakref. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117735 91177308-0d34-0410-b5e6-96231b3b80d8
2010-10-29 23:09:31 +00:00
.long sym6
Tests that now pass. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@115622 91177308-0d34-0410-b5e6-96231b3b80d8
2010-10-05 15:43:32 +00:00
.section .rodata.str1.1,"aMS",@progbits,1
.Lsym7:
.Lsym8:
.text
movsd .Lsym8(%rip), %xmm1
// CHECK: ('_symbols', [
Fixing r116753 r116756 r116777 The failures in r116753 r116756 were caused by a python issue - Python likes to append 'L' suffix to stringified numbers if the number is larger than a machine int. Unfortunately, this causes a divergence of behavior between 32 and 64 bit python versions. I re-crafted elf-dump/common_dump to take care of these issues by: 1. always printing 0x (makes for easy sed/regex) 2. always print fixed length (exactly 2 + numBits/4 digits long) by mod ((2^numBits) - 1) 3. left-padded with '0' There is a residual common routine that is also used by macho-dump (dataToHex) , so I left the 'section_data' test values alone. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@116823 91177308-0d34-0410-b5e6-96231b3b80d8
2010-10-19 17:39:10 +00:00
// CHECK-NEXT: # Symbol 0x00000000
// CHECK-NEXT: (('st_name', 0x00000000) # ''
// CHECK: # Symbol 0x00000001
// CHECK-NEXT: (('st_name', 0x0000000d) # '.Lsym8'
// CHECK: # Symbol 0x00000002
// CHECK-NEXT: (('st_name', 0x00000000) # ''
// CHECK: # Symbol 0x00000003
// CHECK-NEXT: (('st_name', 0x00000000) # ''
// CHECK: # Symbol 0x00000004
// CHECK-NEXT: (('st_name', 0x00000000) # ''
// CHECK: # Symbol 0x00000005
// CHECK-NEXT: (('st_name', 0x00000000) # ''
// CHECK: # Symbol 0x00000006
// CHECK-NEXT: (('st_name', 0x00000001) # '.Lsym1'
// CHECK: # Symbol 0x00000007
// CHECK-NEXT: (('st_name', 0x00000008) # 'sym6'
// CHECK-NEXT: ('st_bind', 0x00000001)
// CHECK-NEXT: ('st_type', 0x00000001)
// CHECK-NEXT: ('st_other', 0x00000000)
// CHECK-NEXT: ('st_shndx', 0x00000000)
Print all 64bits for st_value and st_size. Adjust tests accordingly. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@122263 91177308-0d34-0410-b5e6-96231b3b80d8
2010-12-20 20:49:43 +00:00
// CHECK-NEXT: ('st_value', 0x0000000000000000)
// CHECK-NEXT: ('st_size', 0x0000000000000000)
Tests that now pass. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@115622 91177308-0d34-0410-b5e6-96231b3b80d8
2010-10-05 15:43:32 +00:00
// CHECK-NEXT: ),
// CHECK-NEXT: ])
Reference in New Issue Copy Permalink