-
Notifications
You must be signed in to change notification settings - Fork 183
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
Update to rust-gpu main #82
Conversation
Thanks for the contribution! Do do Rust shaders actually compile for you with this PR? Ignoring the
|
Yes, i've compiled shaders but see no difference after that. But otherwise it compiles without an error (if you set default toolchain to specific nightly) |
Ah, I see, so won't work with |
@h3r2tic @SneakyBerry Hi, just saw this randomly and wanted to quickly check: any reason not to use the latest release ( (See also https://github.com/EmbarkStudios/rust-gpu/releases) I will note, however, that before Rust-GPU 0.10 comes out (hopefully soon), you'll want this: [patch.crates-io]
# HACK(eddyb) using https://github.com/EmbarkStudios/spirt/pull/48 before a new release.
spirt = { git = "https://github.com/EmbarkStudios/spirt", rev = "521c2418076309a4aee9b949a00e77dcbe2fc6b1" } To specifically get this fix (it's been a long-time problem, but recent Rust-GPU has exacerbated it): With that fix, Rust-GPU loops should match HLSL/DXC semantics (I'd almost say "exactly" but idk if there's some edge cases I'm unfamiliar with). |
Thanks for the hint, @eddyb! 🙇 Not much has happened in |
Checklist
Description of Changes
Update dependencies and rust toolchain to rust-gpu main HEAD