Skip to content

Commit

Permalink
spirv-tools: Update to v2024.3+git.8b39a8b
Browse files Browse the repository at this point in the history
Signed-off-by: Ikey Doherty <[email protected]>
  • Loading branch information
ikeycode committed Jan 9, 2025
1 parent f5ca29e commit 690331e
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 6 deletions.
Binary file modified s/spirv-tools/manifest.x86_64.bin
Binary file not shown.
5 changes: 2 additions & 3 deletions s/spirv-tools/manifest.x86_64.jsonc
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,6 @@
"spirv-tools"
],
"files": [
"/usr/include/spirv-tools/instrument.hpp",
"/usr/include/spirv-tools/libspirv.h",
"/usr/include/spirv-tools/libspirv.hpp",
"/usr/include/spirv-tools/linker.hpp",
Expand Down Expand Up @@ -212,6 +211,6 @@
}
},
"source-name": "spirv-tools",
"source-release": "7",
"source-version": "vulkan-sdk-1.3.296.0"
"source-release": "8",
"source-version": "2024.3+git.8b39a8b"
}
6 changes: 3 additions & 3 deletions s/spirv-tools/stone.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@
# SPDX-License-Identifier: MPL-2.0
#
name : spirv-tools
version : vulkan-sdk-1.3.296.0
release : 7
version : 2024.3+git.8b39a8b
release : 8
homepage : https://github.com/KhronosGroup/SPIRV-Tools
upstreams :
- https://github.com/KhronosGroup/SPIRV-Tools/archive/refs/tags/vulkan-sdk-1.3.296.0.tar.gz: 75aafdf7e731b4b6bfb36a590ddfbb38ebc605d80487f38254da24fe0cb95837
- git|https://github.com/KhronosGroup/SPIRV-Tools.git: 8b39a8b54d55c8737196cdce705f32f94d3b2463
summary : The SPIR-V Tools project provides an API and commands for processing SPIR-V modules.
description : |
The project includes an assembler, binary module parser, disassembler, validator, and optimizer for SPIR-V. Except for the optimizer, all are based on a common static library. The library contains all of the implementation details, and is used in the standalone tools whilst also enabling integration into other code bases directly. The optimizer implementation resides in its own library, which depends on the core library.
Expand Down

0 comments on commit 690331e

Please sign in to comment.