llvm-capstone/llvm/test/Linker/commandline.ll

; RUN: llvm-link %S/Inputs/commandline.a.ll %S/Inputs/commandline.b.ll -S | FileCheck %s

; Verify that multiple input llvm.commandline metadata are linked together.

; CHECK-DAG: !llvm.commandline = !{!0, !1, !2}
; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v1"}
; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v2"}
; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v3"}
Implement -frecord-command-line (-frecord-gcc-switches) Implement options in clang to enable recording the driver command-line in an ELF section. Implement a new special named metadata, llvm.commandline, to support frontends embedding their command-line options in IR/ASM/ELF. This differs from the GCC implementation in some key ways: * In GCC there is only one command-line possible per compilation-unit, in LLVM it mirrors llvm.ident and multiple are allowed. * In GCC individual options are separated by NULL bytes, in LLVM entire command-lines are separated by NULL bytes. The advantage of the GCC approach is to clearly delineate options in the face of embedded spaces. The advantage of the LLVM approach is to support merging multiple command-lines unambiguously, while handling embedded spaces with escaping. Differential Revision: https://reviews.llvm.org/D54487 Clang Differential Revision: https://reviews.llvm.org/D54489 llvm-svn: 349155 2018-12-14 15:38:15 +00:00			`; RUN: llvm-link %S/Inputs/commandline.a.ll %S/Inputs/commandline.b.ll -S \| FileCheck %s`

			`; Verify that multiple input llvm.commandline metadata are linked together.`

			`; CHECK-DAG: !llvm.commandline = !{!0, !1, !2}`
			`; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v1"}`
			`; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v2"}`
			`; CHECK-DAG: !{{[0-2]}} = !{!"compiler -v3"}`