maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Feature/elf-linker-options.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

18 lines
489 B
LLVM
Raw Normal View History

CodeGen: support an extension to pass linker options on ELF Introduce an extension to support passing linker options to the linker. These would be ignored by older linkers, but newer linkers which support this feature would be able to process the linker. Emit a special discarded section `.linker-option`. The content of this section is a pair of strings (key, value). The key is a type identifier for the parameter. This allows for an argument free parameter that will be processed by the linker with the value being the parameter. As an example, `lib` identifies a library to be linked against, traditionally the `-l` argument for Unix-based linkers with the parameter being the library name. Thanks to James Henderson, Cary Coutant, Rafael Espinolda, Sean Silva for the valuable discussion on the design of this feature. llvm-svn: 323783
2018-01-31 00:29:29 +08:00
; RUN: llc -mtriple x86_64-elf -filetype asm -o - %s | FileCheck %s
Mark two tests REQUIRES: x86-registered-backend These were introduced in r323783 and use an X86 triple. I'll follow up on the list to check if it would make more sense to remove the triple and mark them REQUIRES: default_triple instead. llvm-svn: 323847
2018-01-31 15:32:03 +08:00
; REQUIRES: x86-registered-target
CodeGen: support an extension to pass linker options on ELF Introduce an extension to support passing linker options to the linker. These would be ignored by older linkers, but newer linkers which support this feature would be able to process the linker. Emit a special discarded section `.linker-option`. The content of this section is a pair of strings (key, value). The key is a type identifier for the parameter. This allows for an argument free parameter that will be processed by the linker with the value being the parameter. As an example, `lib` identifies a library to be linked against, traditionally the `-l` argument for Unix-based linkers with the parameter being the library name. Thanks to James Henderson, Cary Coutant, Rafael Espinolda, Sean Silva for the valuable discussion on the design of this feature. llvm-svn: 323783
2018-01-31 00:29:29 +08:00
!llvm.linker.options = !{!0, !1}
!0 = !{!"option 0", !"value 0"}
!1 = !{!"option 1", !"value 1"}
; CHECK: .section ".linker-options","e",@llvm_linker_options
; CHECK-NEXT: .ascii "option 0"
; CHECK-NEXT: .byte 0
; CHECK-NEXT: .ascii "value 0"
; CHECK-NEXT: .byte 0
; CHECK-NEXT: .ascii "option 1"
; CHECK-NEXT: .byte 0
; CHECK-NEXT: .ascii "value 1"
; CHECK-NEXT: .byte 0