- Aug 18, 2021
-
-
Dzmitry Malyshau authored
-
João Capucho authored
-
João Capucho authored
-
Dzmitry Malyshau authored
-
- Aug 17, 2021
-
-
Connor Fitzgerald authored
-
Connor Fitzgerald authored
-
João Capucho authored
-
João Capucho authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
- Aug 16, 2021
-
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Jim Blandy authored
There's no need for functions that construct SPIR-V types to be fallible, or for their callers to check for errors. As a consequence of this change, there may be other functions that no longer need to be fallible, but Rust doesn't warn and Clippy doesn't lint, so we'll have to address them as they come up.
-
João Capucho authored
-
Dzmitry Malyshau authored
-
Kneelawk authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
- Aug 14, 2021
-
-
Dzmitry Malyshau authored
-
- Aug 13, 2021
-
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
- Aug 12, 2021
-
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
- Aug 11, 2021
-
-
Jim Blandy authored
Some SPIR-V texture access instructions take coordinates as integers, others as floats. The types of coordinates in Naga expressions generally match those in SPIR-V, but Naga indices for arrayed textures are always integers, whereas SPIR-V combines coordinates and array indices into a single vector, so indices need to be cast to match the coordinate component type. This commit makes `write_texture_coordinates` properly cast array indices to match the coordinates' component type before combining them all into a single result vector. Fixes #1186.
-
Alex Es authored
* Proof of concept for "span" feature, with WGSL parsing augmented. * Review: 1) add_span was actually a bad idea, make it set_span and add set_span_if_unknown too. 2) panics on getting/setting span for invalid handles. 3) only set span for constants with a name 4) don't overwrite spans for types. * Added spans to blocks & more expressions getting spans in frontends. Definitely the shotgunny type of commit, but what can you do. The design I went with made spans mandatory to specify, so I had to go and wire them through wherever I could. * Moved Block to a separate module, +clippy * More spans for types in GLSL. * Remove pointless body method. * Make Arena interface require spans. Another shotgun commit, oh boy... * Fix tests. My loathsome habit to "quickly fix things along the way" made a lot of extra work for me here, having to fix my "fixes" for WGSL parser. * Rustfmt + clippy. * Fix compile-errors with span feature enabled. * Nuked set_span* from orbit. Deleting code feels great! * Code review - move feature flags inside functions. * Fix build with "deserialize" feature enabled.
-
Jim Blandy authored
In `back::spv::Writer::write_texture_coordinates`, OpCompositeConstruct can concatenate scalars and vectors, so when combining coordinates with an array index, there is no need to extract the coordinate vector's components individually: once the index has been converted to the appropriate component type, it can be combined with the coordinates in a single instruction.
-
Jim Blandy authored
No intended change in behavior.
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
Dzmitry Malyshau authored
-
- Aug 10, 2021
-
-
Connor Fitzgerald authored
-