hey! this is a static git repo viewer. commit diffs, file history, older commits and other revisions won't load without javascript.

you are still able to view source files on branch tips, but the experience is degraded.

yum-mirror/slang

Making it easier to work with shaders

git clone https://git.yummers.dev/yum-mirror/slang

Jay KwakMake the issue headings bigger (#8143)047b8af482025-08-12

renderedcode

name: Compiler Bug about: Report a bug or unexpected behavior of the Slang compiler / API. title: '' labels: '' assignees: ''

Issue Description

A clear and concise description of what the bug is. Before filing the issue, please make sure the bug can be reproduced with the latest release of Slang.

Reproducer Code

If the issue can be reproduced with a simple code, include the self-contained Slang code along with a slangc commandline invocation, or the C++ code that calls the Slang API to compile the code.

Expected Behavior

A clear and concise description of what you expected to happen, e.g. code should compile successfully, resulting SPIRV should have XXX opcode/capability.

Actual Behavior

A clear and concise description of what actually happened.

Environment

Slang Version (release version number or commit hash)
OS
GPU/Driver version, if the bug is a runtime result error.
Any related environment variables.

Additional context

Add any other context about the problem here.

1---
2name: Compiler Bug
3about: Report a bug or unexpected behavior of the Slang compiler / API.
4title: ''
5labels: ''
6assignees: ''
7
8---
9
10# Issue Description
11A clear and concise description of what the bug is.
12Before filing the issue, please make sure the bug can be reproduced with the latest release of Slang.
13
14# Reproducer Code
15If the issue can be reproduced with a simple code, include the **self-contained** Slang code along with a `slangc` commandline invocation, or the C++ code that calls the Slang API to compile the code.
16
17# Expected Behavior
18A clear and concise description of what you expected to happen, e.g. code should compile successfully, resulting SPIRV should have XXX opcode/capability.
19
20# Actual Behavior
21A clear and concise description of what actually happened.
22
23# Environment
24 - Slang Version (release version number or commit hash)
25 - OS
26 - GPU/Driver version, if the bug is a runtime result error.
27 - Any related environment variables.
28
29# Additional context
30Add any other context about the problem here.