maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/AMDGPU/unify-metadata.ll

28 lines
1.1 KiB
LLVM
Raw Normal View History

[AMDGPU] Add amdgpu-unify-metadata pass Multiple metadata values for records such as opencl.ocl.version, llvm.ident and similar are created after linking several modules. For some of them, notably opencl.ocl.version, this creates semantic problem because we cannot tell which version of OpenCL the composite module conforms. Moreover, such repetitions of identical values often create a huge list of unneeded metadata, which grows bitcode size both in memory and stored on disk. It can go up to several Mb when linked against our OpenCL library. Lastly, such long lists obscure reading of dumped IR. The pass unifies metadata after linking. Differential Revision: https://reviews.llvm.org/D25381 llvm-svn: 289092
2016-12-09 03:46:04 +08:00
; RUN: opt -mtriple=amdgcn--amdhsa -amdgpu-unify-metadata -S < %s | FileCheck -check-prefix=ALL %s
; This test check that we have a singe metadata value after linking several
; modules for records such as opencl.ocl.version, llvm.ident and similar.
; ALL-DAG: !opencl.ocl.version = !{![[OCL_VER:[0-9]+]]}
[AMDGPU] When unifying metadata, add operands to named metadata individually Differential Revision: https://reviews.llvm.org/D27725 llvm-svn: 290114
2016-12-20 00:54:24 +08:00
; ALL-DAG: !llvm.ident = !{![[LLVM_IDENT_0:[0-9]+]], ![[LLVM_IDENT_1:[0-9]+]]}
; ALL-DAG: !opencl.used.extensions = !{![[USED_EXT_0:[0-9]+]], ![[USED_EXT_1:[0-9]+]], ![[USED_EXT_2:[0-9]+]]}
[AMDGPU] Add amdgpu-unify-metadata pass Multiple metadata values for records such as opencl.ocl.version, llvm.ident and similar are created after linking several modules. For some of them, notably opencl.ocl.version, this creates semantic problem because we cannot tell which version of OpenCL the composite module conforms. Moreover, such repetitions of identical values often create a huge list of unneeded metadata, which grows bitcode size both in memory and stored on disk. It can go up to several Mb when linked against our OpenCL library. Lastly, such long lists obscure reading of dumped IR. The pass unifies metadata after linking. Differential Revision: https://reviews.llvm.org/D25381 llvm-svn: 289092
2016-12-09 03:46:04 +08:00
; ALL-DAG: ![[OCL_VER]] = !{i32 1, i32 2}
[AMDGPU] When unifying metadata, add operands to named metadata individually Differential Revision: https://reviews.llvm.org/D27725 llvm-svn: 290114
2016-12-20 00:54:24 +08:00
; ALL-DAG: ![[LLVM_IDENT_0]] = !{!"clang version 4.0"}
; ALL-DAG: ![[LLVM_IDENT_1]] = !{!"clang version 4.0 (rLXXXXXX)"}
; ALL-DAG: ![[USED_EXT_0]] = !{!"cl_images"}
; ALL-DAG: ![[USED_EXT_1]] = !{!"cl_khr_fp16"}
; ALL-DAG: ![[USED_EXT_2]] = !{!"cl_doubles"}
[AMDGPU] Add amdgpu-unify-metadata pass Multiple metadata values for records such as opencl.ocl.version, llvm.ident and similar are created after linking several modules. For some of them, notably opencl.ocl.version, this creates semantic problem because we cannot tell which version of OpenCL the composite module conforms. Moreover, such repetitions of identical values often create a huge list of unneeded metadata, which grows bitcode size both in memory and stored on disk. It can go up to several Mb when linked against our OpenCL library. Lastly, such long lists obscure reading of dumped IR. The pass unifies metadata after linking. Differential Revision: https://reviews.llvm.org/D25381 llvm-svn: 289092
2016-12-09 03:46:04 +08:00
!opencl.ocl.version = !{!1, !0, !0, !0}
[AMDGPU] When unifying metadata, add operands to named metadata individually Differential Revision: https://reviews.llvm.org/D27725 llvm-svn: 290114
2016-12-20 00:54:24 +08:00
!llvm.ident = !{!2, !2, !2, !2, !6}
[AMDGPU] Add amdgpu-unify-metadata pass Multiple metadata values for records such as opencl.ocl.version, llvm.ident and similar are created after linking several modules. For some of them, notably opencl.ocl.version, this creates semantic problem because we cannot tell which version of OpenCL the composite module conforms. Moreover, such repetitions of identical values often create a huge list of unneeded metadata, which grows bitcode size both in memory and stored on disk. It can go up to several Mb when linked against our OpenCL library. Lastly, such long lists obscure reading of dumped IR. The pass unifies metadata after linking. Differential Revision: https://reviews.llvm.org/D25381 llvm-svn: 289092
2016-12-09 03:46:04 +08:00
!opencl.used.extensions = !{!3, !3, !4, !5}
!0 = !{i32 2, i32 0}
!1 = !{i32 1, i32 2}
[AMDGPU] When unifying metadata, add operands to named metadata individually Differential Revision: https://reviews.llvm.org/D27725 llvm-svn: 290114
2016-12-20 00:54:24 +08:00
!2 = !{!"clang version 4.0"}
[AMDGPU] Add amdgpu-unify-metadata pass Multiple metadata values for records such as opencl.ocl.version, llvm.ident and similar are created after linking several modules. For some of them, notably opencl.ocl.version, this creates semantic problem because we cannot tell which version of OpenCL the composite module conforms. Moreover, such repetitions of identical values often create a huge list of unneeded metadata, which grows bitcode size both in memory and stored on disk. It can go up to several Mb when linked against our OpenCL library. Lastly, such long lists obscure reading of dumped IR. The pass unifies metadata after linking. Differential Revision: https://reviews.llvm.org/D25381 llvm-svn: 289092
2016-12-09 03:46:04 +08:00
!3 = !{!"cl_images", !"cl_khr_fp16"}
!4 = !{!"cl_images", !"cl_doubles"}
!5 = !{}
[AMDGPU] When unifying metadata, add operands to named metadata individually Differential Revision: https://reviews.llvm.org/D27725 llvm-svn: 290114
2016-12-20 00:54:24 +08:00
!6 = !{!"clang version 4.0 (rLXXXXXX)"}