maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/mlir/test/Target/SPIRV/global-variable.mlir

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

37 lines
1.7 KiB
MLIR
Raw Normal View History

[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
// RUN: mlir-translate -test-spirv-roundtrip -split-input-file %s | FileCheck %s
[MLIR][SPIRV] Rename `spv.globalVariable` to `spv.GlobalVariable`. To unify the naming scheme across all ops in the SPIR-V dialect, we are moving from spv.camelCase to spv.CamelCase everywhere. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D97919
2021-03-05 05:17:12 +08:00
// CHECK: spv.GlobalVariable @var0 bind(1, 0) : !spv.ptr<f32, Input>
// CHECK-NEXT: spv.GlobalVariable @var1 bind(0, 1) : !spv.ptr<f32, Output>
// CHECK-NEXT: spv.GlobalVariable @var2 built_in("GlobalInvocationId") : !spv.ptr<vector<3xi32>, Input>
// CHECK-NEXT: spv.GlobalVariable @var3 built_in("GlobalInvocationId") : !spv.ptr<vector<3xi32>, Input>
[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
[mlir][spirv] Use spv.vce in spv.module and wire up (de)serialization This commits changes the definition of spv.module to use the #spv.vce attribute for specifying (version, capabilities, extensions) triple so that we can have better API and custom assembly form. Since now we have proper modelling of the triple, (de)serialization is wired up to use them. With the new UpdateVCEPass, we don't need to manually specify the required extensions and capabilities anymore when creating a spv.module. One just need to call UpdateVCEPass before serialization to get the needed version/extensions/capabilities. Differential Revision: https://reviews.llvm.org/D75872
2020-03-12 04:04:25 +08:00
spv.module Logical GLSL450 requires #spv.vce<v1.0, [Shader], []> {
[MLIR][SPIRV] Rename `spv.globalVariable` to `spv.GlobalVariable`. To unify the naming scheme across all ops in the SPIR-V dialect, we are moving from spv.camelCase to spv.CamelCase everywhere. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D97919
2021-03-05 05:17:12 +08:00
spv.GlobalVariable @var0 bind(1, 0) : !spv.ptr<f32, Input>
spv.GlobalVariable @var1 bind(0, 1) : !spv.ptr<f32, Output>
spv.GlobalVariable @var2 {built_in = "GlobalInvocationId"} : !spv.ptr<vector<3xi32>, Input>
spv.GlobalVariable @var3 built_in("GlobalInvocationId") : !spv.ptr<vector<3xi32>, Input>
[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
}
// -----
[mlir][spirv] Use spv.vce in spv.module and wire up (de)serialization This commits changes the definition of spv.module to use the #spv.vce attribute for specifying (version, capabilities, extensions) triple so that we can have better API and custom assembly form. Since now we have proper modelling of the triple, (de)serialization is wired up to use them. With the new UpdateVCEPass, we don't need to manually specify the required extensions and capabilities anymore when creating a spv.module. One just need to call UpdateVCEPass before serialization to get the needed version/extensions/capabilities. Differential Revision: https://reviews.llvm.org/D75872
2020-03-12 04:04:25 +08:00
spv.module Logical GLSL450 requires #spv.vce<v1.0, [Shader], []> {
[MLIR][SPIRV] Rename `spv.globalVariable` to `spv.GlobalVariable`. To unify the naming scheme across all ops in the SPIR-V dialect, we are moving from spv.camelCase to spv.CamelCase everywhere. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D97919
2021-03-05 05:17:12 +08:00
// CHECK: spv.GlobalVariable @var1 : !spv.ptr<f32, Input>
// CHECK-NEXT: spv.GlobalVariable @var2 initializer(@var1) bind(1, 0) : !spv.ptr<f32, Input>
spv.GlobalVariable @var1 : !spv.ptr<f32, Input>
spv.GlobalVariable @var2 initializer(@var1) bind(1, 0) : !spv.ptr<f32, Input>
[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
}
// -----
[mlir][spirv] Use spv.vce in spv.module and wire up (de)serialization This commits changes the definition of spv.module to use the #spv.vce attribute for specifying (version, capabilities, extensions) triple so that we can have better API and custom assembly form. Since now we have proper modelling of the triple, (de)serialization is wired up to use them. With the new UpdateVCEPass, we don't need to manually specify the required extensions and capabilities anymore when creating a spv.module. One just need to call UpdateVCEPass before serialization to get the needed version/extensions/capabilities. Differential Revision: https://reviews.llvm.org/D75872
2020-03-12 04:04:25 +08:00
spv.module Logical GLSL450 requires #spv.vce<v1.0, [Shader], []> {
[MLIR][SPIRV] Rename `spv.globalVariable` to `spv.GlobalVariable`. To unify the naming scheme across all ops in the SPIR-V dialect, we are moving from spv.camelCase to spv.CamelCase everywhere. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D97919
2021-03-05 05:17:12 +08:00
spv.GlobalVariable @globalInvocationID built_in("GlobalInvocationId") : !spv.ptr<vector<3xi32>, Input>
[mlir][spirv] Introduce spv.func Thus far we have been using builtin func op to model SPIR-V functions. It was because builtin func op used to have special treatment in various parts of the core codebase (e.g., pass pipelines, etc.) and it's easy to bootstrap the development of the SPIR-V dialect. But nowadays with general op concepts and region support we don't have such limitations and it's time to tighten the SPIR-V dialect for completeness. This commits introduces a spv.func op to properly model SPIR-V functions. Compared to builtin func op, it can provide the following benefits: * We can control the full op so we can integrate SPIR-V information bits (e.g., function control) in a more integrated way and define our own assembly form and enforcing better verification. * We can have a better dialect and library boundary. At the current moment only functions are modelled with an external op. With this change, all ops modelling SPIR-V concpets will be spv.* ops and registered to the SPIR-V dialect. * We don't need to special-case func op anymore when creating ConversionTarget declaring SPIR-V dialect as legal. This is quite important given we'll see more and more conversions in the future. In the process, bumps a few FuncOp methods to the FunctionLike trait. Differential Revision: https://reviews.llvm.org/D74226
2020-02-08 00:30:19 +08:00
spv.func @foo() "None" {
[MLIR][SPIRV] Rename `spv._address_of` to `spv.mlir.addressof` This commit does the renaming mentioned in the title in order to bring `spv` dialect closer to the MLIR naming conventions. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D91609
2020-11-18 00:45:32 +08:00
// CHECK: %[[ADDR:.*]] = spv.mlir.addressof @globalInvocationID : !spv.ptr<vector<3xi32>, Input>
%0 = spv.mlir.addressof @globalInvocationID : !spv.ptr<vector<3xi32>, Input>
[MLIR][SPIRV] Rename `spv.constant` to `spv.Constant`. To unify the naming scheme across all ops in the SPIR-V dialect, we are moving from `spv.camelCase` to `spv.CamelCase` everywhere. Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D97917
2021-03-05 05:15:46 +08:00
%1 = spv.Constant 0: i32
[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
// CHECK: spv.AccessChain %[[ADDR]]
[mlir][spirv] Enhance AccessChainOp index type handling This patch extends the AccessChainOp index type handling to be able to deal with all Integer type indices (i.e., all bit-widths and signedness symantics). There were two ways of achieving this: 1- Backward compatible: The new way of handling the indices will assume that an index type is i32 by default if not specified in the assembly format, this way all the old tests would pass correctly. 2- Enforce the format: This unifies the spv.AccessChain Op format and all the old tests had to be updated to reflect this change or else they fail. I picked option-2 to unify the Op format and avoid having optional index-type fields that can lead to somewhat confusing tests format and multiple representations for the same Op with undocumented assumption that an index is i32 unless stated. Nonetheless, reverting to option-1 should be straightforward if preferred or needed. Differential Revision: https://reviews.llvm.org/D81763
2020-06-22 22:04:53 +08:00
%2 = spv.AccessChain %0[%1] : !spv.ptr<vector<3xi32>, Input>, i32
[spirv] NFC: clean up (de)serialization tests This CL uses the newly added -split-input-file CLI option to mlir-translate to combine certain (de)serialization tests. It also renames certain test filenames. PiperOrigin-RevId: 270816324
2019-09-24 10:56:49 +08:00
spv.Return
}
}