Skip to content

Add spirv patch for split barrier support #330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 25, 2022
Merged

Add spirv patch for split barrier support #330

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions patches/spirv/0001-update-SPIR-V-headers-for-SPV_INTEL_split_barrier.patch
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
From 05dbb133140653f21efc1feebfcb614386cc2a62 Mon Sep 17 00:00:00 2001
From: Feng Zou <[email protected]>
Date: Fri, 25 Feb 2022 13:51:07 +0800
Subject: [PATCH] update SPIR-V headers for SPV_INTEL_split_barrier

PR:https://github.com/KhronosGroup/SPIRV-Headers/pull/268
---
lib/SPIRV/libSPIRV/spirv.hpp | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/lib/SPIRV/libSPIRV/spirv.hpp b/lib/SPIRV/libSPIRV/spirv.hpp
index cbe5a94c..631396b8 100644
--- a/lib/SPIRV/libSPIRV/spirv.hpp
+++ b/lib/SPIRV/libSPIRV/spirv.hpp
@@ -983,6 +983,7 @@ enum Capability {
CapabilityAtomicFloat64AddEXT = 6034,
CapabilityFastCompositeINTEL = 6093,
CapabilityOptNoneINTEL = 6094,
+ CapabilitySplitBarrierINTEL = 6141,
CapabilityMax = 0x7fffffff,
};

@@ -1538,6 +1539,8 @@ enum Op {
OpFPGARegINTEL = 5949,
OpAtomicFAddEXT = 6035,
OpTypeBufferSurfaceINTEL = 6086,
+ OpControlBarrierArriveINTEL = 6142,
+ OpControlBarrierWaitINTEL = 6143,
OpMax = 0x7fffffff,
};

@@ -2076,6 +2079,8 @@ inline void HasResultAndType(Op opcode, bool *hasResult, bool *hasResultType) {
*hasResult = true;
*hasResultType = false;
break;
+ case SpvOpControlBarrierArriveINTEL: *hasResult = false; *hasResultType = false; break;
+ case SpvOpControlBarrierWaitINTEL: *hasResult = false; *hasResultType = false; break;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this clang-formatted?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Most of case statements are in one line, except the one in line 2078 ~ 2081. So I follow the code format in most of lines.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

}
}
#endif /* SPV_ENABLE_UTILITY_CODE */
--
2.18.1