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/AArch64/directive-variant_pcs-err.s

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

12 lines
332 B
ArmAsm
Raw Normal View History

[AArch64] Implement .variant_pcs directive A dynamic linker with lazy binding support may need to handle variant PCS function symbols specially, so an ELF symbol table marking STO_AARCH64_VARIANT_PCS [1] was added to address this. Function symbols that follow the vector PCS are marked via the .variant_pcs assembler directive, which takes a single parameter specifying the symbol name and sets the STO_AARCH64_VARIANT_PCS st_other flag in the object file. [1] https://github.com/ARM-software/abi-aa/blob/master/aaelf64/aaelf64.rst#st-other-values Reviewed By: sdesmalen Differential Revision: https://reviews.llvm.org/D89138
2020-10-08 22:51:10 +08:00
// RUN: not llvm-mc -triple aarch64-unknown-none-eabi -filetype asm -o - %s 2>&1 | FileCheck %s
[AArch64][MC] Remove unneeded "in .xxx directive" from diagnostics The prevailing style does not add the message. The directive name is not useful because the next line replicates the error line which includes the directive.
2021-05-24 04:58:16 +08:00
// CHECK: [[#@LINE+1]]:13: error: expected symbol name
[AArch64] Implement .variant_pcs directive A dynamic linker with lazy binding support may need to handle variant PCS function symbols specially, so an ELF symbol table marking STO_AARCH64_VARIANT_PCS [1] was added to address this. Function symbols that follow the vector PCS are marked via the .variant_pcs assembler directive, which takes a single parameter specifying the symbol name and sets the STO_AARCH64_VARIANT_PCS st_other flag in the object file. [1] https://github.com/ARM-software/abi-aa/blob/master/aaelf64/aaelf64.rst#st-other-values Reviewed By: sdesmalen Differential Revision: https://reviews.llvm.org/D89138
2020-10-08 22:51:10 +08:00
.variant_pcs
[AArch64][MC] Remove unneeded "in .xxx directive" from diagnostics The prevailing style does not add the message. The directive name is not useful because the next line replicates the error line which includes the directive.
2021-05-24 04:58:16 +08:00
// CHECK: [[#@LINE+1]]:14: error: unknown symbol
[AArch64] Implement .variant_pcs directive A dynamic linker with lazy binding support may need to handle variant PCS function symbols specially, so an ELF symbol table marking STO_AARCH64_VARIANT_PCS [1] was added to address this. Function symbols that follow the vector PCS are marked via the .variant_pcs assembler directive, which takes a single parameter specifying the symbol name and sets the STO_AARCH64_VARIANT_PCS st_other flag in the object file. [1] https://github.com/ARM-software/abi-aa/blob/master/aaelf64/aaelf64.rst#st-other-values Reviewed By: sdesmalen Differential Revision: https://reviews.llvm.org/D89138
2020-10-08 22:51:10 +08:00
.variant_pcs foo
.global foo
[AArch64][MC] Remove unneeded "in .xxx directive" from diagnostics The prevailing style does not add the message. The directive name is not useful because the next line replicates the error line which includes the directive.
2021-05-24 04:58:16 +08:00
// CHECK: [[#@LINE+1]]:18: error: expected newline
[AArch64] Implement .variant_pcs directive A dynamic linker with lazy binding support may need to handle variant PCS function symbols specially, so an ELF symbol table marking STO_AARCH64_VARIANT_PCS [1] was added to address this. Function symbols that follow the vector PCS are marked via the .variant_pcs assembler directive, which takes a single parameter specifying the symbol name and sets the STO_AARCH64_VARIANT_PCS st_other flag in the object file. [1] https://github.com/ARM-software/abi-aa/blob/master/aaelf64/aaelf64.rst#st-other-values Reviewed By: sdesmalen Differential Revision: https://reviews.llvm.org/D89138
2020-10-08 22:51:10 +08:00
.variant_pcs foo bar