-
Notifications
You must be signed in to change notification settings - Fork 46
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
GEP not implemented for type struct [_; 0] #151
Comments
Is it alright if I check this out? |
Feel free to give it a try. This old patch won't be directly cherry-pickable due to some larger gep changes. |
I'm a bit confused what should be emitted, since it doesn't make sense to have a GEP to an array with zero elements. Should it just emit a constant value? For context I added the patch you linked here (which is very WIP), but it still fails with this: Ah I realize we're hitting this because we're emitting a struct and not an array now |
std::process::Command.output() doesn't return error on non-zero exit, only when command.inner() fails. If `which nvcc` can't find `nvcc` it returns like (ExitStatus(-1), "", "") and causes a panic in the return of the function. Instead, panic on non-zero return with an informational diagnostic message.
Original issue: EmbarkStudios/rust-gpu#1075
Expected Behaviour
This compiles fine with rustc (I guess this bit is probably eliminated?).
Example & Steps To Reproduce
I was using const generic parameters to determine the length of some arrays. At some point, a base case ended up declaring a zero-length array, like so:
Resulting in:
System Info
The text was updated successfully, but these errors were encountered: