Debian Patches
Status for spirv-llvm-translator-22/22.1.7-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0002-Backport-to-22-Implement-extension-SPV_KHR_float_con.patch | [02/13] [Backport to 22] Implement extension SPV_KHR_float_controls2 (#3475) First attempt at implementing [SPV_KHR_float_controls2](https://github.khronos.org/SPIRV-Registry/extensions/KHR/SPV_KHR_float_controls2.html). - When doing SPIRV->LLVM-IR, we first read the `ExecutionModeFPFastMathDefault` for every kernel, and if instructions in that kernel do not specify a particular `FPFastMathMode`, we use the kernel one. - `ExecutionModeFPFastMathDefault` is **not** propagated down to the callees. - According to [SPV_KHR_float_controls2#issues](https://github.khronos.org/SPIRV-Registry/extensions/KHR/SPV_KHR_float_controls2.html#_issues); we do not have an equivalent of LLVM's `afn` flag. If we map `fadd fast float %a, %b` to SPIRV and back, it becomes `fadd reassoc nnan ninf nsz arcp contract float %a, %b` losing the `afn` flag. - `ContractionOff` and `SignedZeroInfNanPreserve` are translated to a `ExecutionModeFPFastMathDefault` with all flags set to 0. |
Juan Manuel Martinez Caamaño | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/dc3a0611215cb7ee481bcca7aad0c7afae763acb | 2026-02-18 | |
| 0003-Backport-to-22-Allow-FPFastMathMode-decoration-on-Op.patch | [03/13] [Backport to 22] Allow FPFastMathMode decoration on OpFmaKHR (#3820) Inspired by https://github.com/llvm/llvm-project/pull/206143 |
Arseniy Obolenskiy <arseniy.obolenskiy@amd.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/39d3c567ef11eac8f8d8010ab24ebf4123dd1102 | 2026-07-09 | |
| 0004-Backport-to-22-Emit-FPFastMathMode-for-Call-3912.patch | [04/13] [Backport to 22] Emit FPFastMathMode for Call (#3912) `SPV_KHR_float_controls2` makes `FPFastMathMode` valid for all core instructions, so this patch enables translation of fast math flags for `OpFunctionCall`. |
Marcos Maronas <mmaronas@amd.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/e24edbd78b78779fc4c99847cf937059dcae234d | 2026-08-03 | |
| 0005-Backport-to-22-DebugInfo-Fix-NonSemantic-DebugTypeBa.patch | [05/13] [Backport to 22] [DebugInfo] Fix NonSemantic DebugTypeBasic Flags operand (#3740) The NonSemantic.Shader.DebugInfo spec requires the Flags operand of DebugTypeBasic to be a 32-bit integer constant. The translator was emitting `DebugInfoNone` instead of `OpConstant 0`. `spirv-val` on the NonSemantic path cannot be enabled yet due to other spec-compliance issues to be fixed in subsequent changes. |
Viktoria Maximova <viktoria.maksimova@intel.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/b1106b6797e392c653aaa0dd016db0aa39cba71c | 2026-05-11 | |
| 0011-Backport-to-22-Disable-spirv-val-in-global_block-tes.patch | [11/13] [Backport to 22] Disable spirv-val in global_block test that fails newer spirv-val (#3680) Some spirv-val invocations are failing with newer SPIRV-Tools (`e4bceacf`) for PtrCastToGeneric OpSpecConstantOps with the error: Expected input and Result Type to point to the same type Disable the spirv-val steps temporarily. |
Sven van Haastregt <sven.vanhaastregt@arm.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/22a1a5be60f672fed2cdf7711ce64031ee33d4d8 | 2026-04-13 | |
| 0001-Backport-to-22-NFC-Allow-llvm-Value-derived-types-on.patch | [01/13] [Backport to 22] [NFC] Allow `llvm::Value` derived types on `SPIRVMDWalker::get` (#3557) This is used later by https://github.com/KhronosGroup/SPIRV-LLVM-Translator/pull/3475 |
Juan Manuel Martinez Caamaño | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/2b26eccd60779a30c588571c84e67a036402b19e | 2026-02-02 | |
| 0006-Backport-to-22-DebugInfo-Fix-NonSemantic-DebugLine-S.patch | [06/13] [Backport to 22] [DebugInfo] Fix NonSemantic DebugLine Source operand (#3747) NonSemantic.Shader.DebugInfo.100/.200 require the Source operand of DebugLine to reference a DebugSource instruction, not a raw OpString ID (DIFile in LLVM IR). Use getSource() to emit a proper DebugSource reference. Enable spirv-val on the NonSemantic paths of DebugInfoTypeBasic.ll and InlineNamespace.ll now that all previous spec-compliance fixes are in place. |
Viktoria Maximova <viktoria.maksimova@intel.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/ad6941b5c5836ba8aa3ba1d0466bc81cfcbd11d7 | 2026-05-13 | |
| 0007-Backport-to-22-DebugInfo-Fix-DebugFunction-Parent-wh.patch | [07/13] [Backport to 22] [DebugInfo] Fix DebugFunction Parent when DISubprogram is scoped in DIModule (#3753) NonSemantic.Shader.DebugInfo requires DebugFunction's Parent operand to be a lexical scope, defined by the spec as one of DebugCompilationUnit, DebugFunction, DebugLexicalBlock, or DebugTypeComposite. DebugModule (introduced in .200) is not a lexical scope, and spirv-val rejects it. When a DISubprogram's scope is a DIModule, fall back to the enclosing DebugCompilationUnit, matching the existing handling for DIFile. |
Viktoria Maximova <viktoria.maksimova@intel.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/d7f4a19bbdadc81b6cb4c30fa0a2e7576f45c768 | 2026-05-18 | |
| 0008-Backport-to-22-Make-DebugLinePriority-test-valid-SPI.patch | [08/13] [Backport to 22] Make DebugLinePriority test valid SPIR-V (#3672) A recent version of SPIRV-Tools found several issues with the test, such as `DebugTypeFunction` having the wrong return type operand and `DebugTypeBasic` missing the flags operand. |
Sven van Haastregt <sven.vanhaastregt@arm.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/0a606ea4219f21117bf4dc1bab6f17427cc18b73 | 2026-03-31 | |
| 0009-Backport-to-22-Avoid-creating-ConstantComposites-wit.patch | [09/13] [Backport to 22] Avoid creating ConstantComposites with spec constants (#3662) A recent version of spirv-val is now reporting "OpConstantComposite must not have spec constant operands" for some tests. Fix by letting `addCompositeConstant` defer to `addSpecConstantComposite` when attempting to add a constant that has one or more specialization constant operands. |
Sven van Haastregt <sven.vanhaastregt@arm.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/e9d0bd15b22ae2db5ce532c71bf2266b9d5821b5 | 2026-03-18 | |
| 0010-Backport-to-22-Disable-spirv-val-in-some-tests-3584.patch | [10/13] [Backport to 22] Disable spirv-val in some tests (#3584) Disable SPIR-V validation in some tests that do not pass with current HEAD of SPIRV-Tools (cb38b234 ("spirv-opt: Add LegalizeMultidim...", 2026-02-11)) while the discussion of #3569 is ongoing. |
Sven van Haastregt <sven.vanhaastregt@arm.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/46a4e7e273d8e3bf20c428f063948349fe03abd7 | 2026-02-16 | |
| 0012-Backport-to-22-Fix-DebugTypeFunction-void-return-typ.patch | [12/13] [Backport to 22] Fix DebugTypeFunction void return type (#3718) All DebugInfo specs (core SPIR-V, OpenCL.DebugInfo.100, NonSemantic.Shader.DebugInfo.*) require the `ReturnType` operand of `DebugTypeFunction` to reference a valid type. For void-returning functions the translator was emitting `DebugInfoNone` instead of `VoidTy`. Also fix the same issue in existing reverse-translation test inputs that were generated by the Writer with the bug in place. `spirv-val` on the NonSemantic path cannot be enabled yet due to other spec-compliance issues to be fixed in subsequent changes. |
Viktoria Maximova <viktoria.maksimova@intel.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/71d1484dd985b2950e3ec09d7e1e4092b2eeae6b | 2026-05-04 | |
| 0013-Backport-to-22-fix-a-spir-val-error-in-the-cooperati.patch | [13/13] [Backport to 22] fix a spir-val error in the cooperative_matrix_constant_null test (#3568) Fixes a validation error reported by recent versions of spirv-val: ``` %8 = OpTypeCooperativeMatrixKHR %uint %3 %uint_12 %uint_12 %3 ``` Basically, the cooperative matrix scope needs to be 2 (Workgroup) or 3 (Subgroup) instead of the current 0 (CrossDevice). Since 3 (Subgroup) is the most common usage, for now at least, I've gone with it. |
Ben Ashbaugh <ben.ashbaugh@intel.com> | no | upstream, https://github.com/KhronosGroup/SPIRV-LLVM-Translator/commit/67b3fc338a3ce0ebce5d249cbc437e8b36ffdeaa | 2026-02-16 | |
| visibility-hidden.patch | reduce the amount of symbols exposed by the library | Andreas Beckmann <anbe@debian.org> | yes |
All known versions for source package 'spirv-llvm-translator-22'
- 22.1.7-1 (sid, forky)
