1639: Doc fixes for wgpu r=cwfitzgerald a=jimblandy
This PR makes `cargo doc --all-features` work without errors.
Commits are organized for ease of review (and for revision, if I screwed something up).
Co-authored-by: Jim Blandy <jimb@red-bean.com>
Change references to `RenderBundleEncoder` in descriptions of `RenderEncoder`
methods to `RenderEncoder` instead, since they all seem to be referring to
methods of this trait, and presumably apply to `RenderPass`es as well.
1634: Improve documentation of ImageDataLayout r=kvark a=cwfitzgerald
**Connections**
Fixes#1626.
**Description**
Just improves the docs.
**Testing**
Docs. @StarArawn take a look if that clears things up.
Co-authored-by: Connor Fitzgerald <connorwadefitzgerald@gmail.com>
1633: Always use EXT Robustness with EGL r=kvark a=cwfitzgerald
**Connections**
Closes#1631. Closes#1577.
**Description**
KHR robustness doesn't seem to work on any real platform. This unconditionally uses EXT robustness.
**Testing**
Works on rpi and my haswell rig. @Gordon-F could you check your android?
Co-authored-by: Connor Fitzgerald <connorwadefitzgerald@gmail.com>
1623: Enable All Backends for Trace Player r=cwfitzgerald a=zicklag
**Connections**
None
**Description**
I just spent a bit of time trying to figure out how to get the trace player to play an OpenGL trace before realizing that only the primary backends were enabled at instance creation. This just enables all backends in the trace player. I believe that this should be harmless as it shouldn't change anything for traces on the primary supported backends.
**Testing**
It's not tested specifically, but it's such a minor change it shouldn't matter, I think.
Co-authored-by: Zicklag <zicklag@katharostech.com>
1612: Update `web-sys` r=grovesNL a=a1phyr
`wgpu` uses unstable APIs so the version has to be pinned and manually updated.
No breaking changes happened in `0.3.51` so this update is easy.
Co-authored-by: Benoît du Garreau <bdgdlm@outlook.com>
1607: Fix Downlevel Vertex Stage Storage Buffer Check r=kvark a=cwfitzgerald
**Connections**
Fixes a bug in #1599. Also follows up on #1583 marking all of hello-compute as a failure.
**Testing**
Tests now pass on rpi4.
Co-authored-by: Connor Fitzgerald <connorwadefitzgerald@gmail.com>
1604: Upgrade `arrayvec` to 0.7 r=kvark a=a1phyr
Upgrade `arrayvec` to version 0.7 (using const generics).
Co-authored-by: Benoît du Garreau <bdgdlm@outlook.com>
1606: Fix macos build r=cwfitzgerald a=scoopr
Building on macos failed with
```
Compiling wgpu-hal v0.9.0 (/Users/scoopr/Code/ext/wgpu/wgpu-hal)
error[E0609]: no field `entry` on type `&vulkan::Instance`
--> /Users/scoopr/Code/ext/wgpu/wgpu-hal/src/vulkan/instance.rs:267:61
|
267 | let metal_loader = ext::MetalSurface::new(&self.entry, &self.shared.raw);
| ^^^^^ unknown field
|
= note: available fields are: `shared`, `extensions`
error: aborting due to previous error
```
The PR fixes the issue.
Co-authored-by: Mikko Lehtonen <scoopr@iki.fi>
1599: Fix Limits for lava/llvmpipe and re-enable and re-work CI r=kvark,groves,wumpf a=cwfitzgerald
**Connections**
No longer fixes#1551.
**Description**
This PR has a couple things going on at once.
- Fixes limits for llvmpipe, lavapipe, and rpi4.
- Added a downlevel limit to express that RPI4 does not allow storage buffers in vertex shaders on GL.
- Added a `Limits::downlevel_default()` that takes minimum limits from GLES and adds some more documentation on how to choose limits.
- Moved all examples to the new downlevel limits
- Reworks CI to re-enable software testing and unify instructions.
**Testing**
It is
Co-authored-by: Connor Fitzgerald <connorwadefitzgerald@gmail.com>
1600: Vulkan Timeline Semaphores r=kvark a=kvark
**Connections**
None
**Description**
One of the non-straightforward design decisions in wgpu-hal was to expose the fences with `D3D12Fence` semantics. Now that we got Vulkan, Metal, and GLES3, it became a bit concerning that all of these backends implemented this new fence API in the same convoluted way: via managing a pool of binary fences internally, which requires maintenance (done on submit() only). If that's the expected implementation, then the abstraction is wrong.
For this reason, it was important for me to try implementing this new semantics in a modern Vulkan way - via timeline semaphores. With this, we have 1:1 relation between `Api::Fence` and a Vulkan object. I believe the experiment is a success: Vulkan is now very efficient at fences!
**Testing**
Works on the examples!
Co-authored-by: Dzmitry Malyshau <dmalyshau@mozilla.com>
1598: Fix memory leak in acquiring encoders r=kvark a=kvark
**Connections**
Fixes#1501Fixes#1531
**Description**
It was ... interesting. We were creating new command encoders all the time, but still trying to add them to the pool to re-use later. So we were constantly allocating and never freeing them, up until the end. Therefore, program as a whole was valid and non-leaking, if analyzed after termination.
**Testing**
Observed memory manually
Co-authored-by: Dzmitry Malyshau <dmalyshau@mozilla.com>
1597: hal/metal: bump storage limits r=kvark a=kvark
**Connections**
Fixes#1596
**Description**
The limits where just copied from the defaults. Then we updated the defaults...
**Testing**
Just ran locally
Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
1594: Generation of memory reports for Hubs r=cwfitzgerald a=kvark
**Connections**
Part of #1501
**Description**
Tried to see if we aren't accidentally growing the hubs.
**Testing**
Examples...
Co-authored-by: Dzmitry Malyshau <kvark@fastmail.com>
1593: Fix VVL on halmark example r=kvark a=kvark
**Connections**
We have a bunch of VVL related to resource destruction on the halmark example.
It also seems to leak memory quite a ton and eventually hang the system.
**Description**
This PR fixes the logic of changing the command pools in halmark, its initialization sequence, and its destruction.
**Testing**
Tested on halmark and others
Co-authored-by: Dzmitry Malyshau <kvark@fastmail.com>
1592: Detailed limits check and error r=cwfitzgerald a=kvark
**Connections**
Related to #1590
**Description**
The old comparison "A < B" was simply wrong, because it would do every field in order and could bail out mid-way without reaching for all limits.
**Testing**
Untested
Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
