-
Notifications
You must be signed in to change notification settings - Fork 248
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.
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
Compiler panics when using #[spirv(object_to_world)] #723
Comments
Thanks for the issue! Looks like the problem is due to some problematic interaction between internal compiler details due to unused parameters. In the meantime, this issue can be worked around via using the parameter in some way (I've not done raytracing stuff before, not sure what form the shader takes or if there's output variables, but something like this): #[spirv(closest_hit)]
pub fn test_closest_hit(#[spirv(object_to_world)] object_to_world: [Vec4; 3], something: &mut f32) {
*something = object_to_world[0].x;
} |
Thanks! I've succeeded to work around compiler panic but I still fail to use
I checked valid SPIR-V emitted by test.rchit
and got
But I couldn't find any way to use |
Ah, shoot, yeah, we currently don't expose OpTypeMatrix. That feature is currently tracked by #82 :( |
Hi, I encountered compiler panic and I report here as output says.
Expected Behaviour
The compiler doesn't panic.
I also want to know how do we use #[spirv(object_to_world)] correctly.
Example & Steps To Reproduce
lib.rs
build.rs
I created a repository for this issue https://github.com/hatoo/rust-gpu-issue.
You can reproduce by clone and build it.
System Info
Backtrace
Backtrace
The text was updated successfully, but these errors were encountered: