shader-playground | Shader playground website for exploring HLSL | Graphics library

by tgjones C Version: Current License: BSD-2-Clause

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | shader-playground Summary

shader-playground is a C library typically used in User Interface, Graphics, WebGL applications. shader-playground has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Shader Playground is a website for exploring shader compilers.

Support

Quality

Security

License

Reuse

Support

shader-playground has a low active ecosystem.

It has 474 star(s) with 43 fork(s). There are 20 watchers for this library.

It had no major release in the last 6 months.

There are 25 open issues and 69 have been closed. On average issues are closed in 199 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of shader-playground is current.

Quality

shader-playground has 0 bugs and 0 code smells.

Security

shader-playground has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

shader-playground code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

shader-playground is licensed under the BSD-2-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

shader-playground releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of shader-playground

Get all kandi verified functions for this library.

shader-playground Key Features

No Key Features are available at this moment for shader-playground.

shader-playground Examples and Code Snippets

No Code Snippets are available at this moment for shader-playground.

Community Discussions

Trending Discussions on shader-playground

What is the problem with generated SPIR-V code and how to verify it?

QUESTION

What is the problem with generated SPIR-V code and how to verify it?

Asked 2020-Jul-08 at 07:41

I have some generated SPIR-V code which I want to use with the vulkan API. But I get an Exception thrown at 0x00007FFB68D933CB (nvoglv64.dll) in vulkanCompute.exe: 0xC0000005: Access violation reading location 0x0000000000000008. when trying to create the pipline with vkCreateComputePipelines.

The API calls should be fine, because the same code works with a shader compiled with glslangValidator. Therefore I assume that the generated SPIR-V code must be illformed somehow.

I've checked the SPIR-V code with the validator tool from khronos, using spirv-val --target-env vulkan1.1 mainV.spv which exited without error. Anyhow it is also known that this tool is still incomplete.

I've also tried to use the Radeon GPU Analyzer to compile my SPIR-V code, which is also available online at the shader playground and this tool throws the error Error: Error: internal error: Bil::BilInstructionConvert::Create(60) Code Not Tested! which is not really helpful, but encourages the assumption that the code is malformed.

The SPIR-V code is unfortunately to long to post it here, but it is in the link of the shader playground.

Does anyone know what the problem is with my setting or has any idea how I can verify my SPIR-V code in a better way, without checking all 700 lines of code manually.

I don't thinkt the problem is there, but anyway here is the c++ host code:

...

ANSWER

Answered 2020-Jul-08 at 07:41

Well after checking out line per line it showed that the problem is when working with pointers of pointers. For me it is still not clear from the specification that it is not allowed, but it is understandable that it does not work with logical pointers. Still the behaviour is strange that the validator is not able to note that and that compiling the SPIRV code crashes instead of throwing a clear error message. So in the end, it was the Shader code which was wrong.

Source https://stackoverflow.com/questions/62713718

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install shader-playground

You can download it from GitHub.

Support

Contributions are gratefully accepted. If you want to add a new compiler, or improve integration with an existing compiler, or any other type of bug fix or improvement to the website, please open an issue.

Find more information at: