Metal vertex buffer stride #2077
Labels
backend: Metal
client: CTS
Has associated Vulkan CTS tests that fail or crash
module: hal
type: discussion
Milestone
Comments
kvark
added
type: bug
module: hal
type: discussion
value: high
backend: Metal
api: ll
client: CTS
This was referenced May 28, 2018
bors bot
added a commit
that referenced
this issue
May 29, 2018
2076: Metal revised memory types r=grovesNL a=kvark Fixes #2069 ~~Includes #2070 (please only review the last 2 commits)~~ The PR effectively removes all the complicated memory allocation tracking from the Metal backend, instead relying on mapping the available storage types (with CPU caching policy) more accurately to what can be represented in Vulkan API. With this in, we slice through the whole `memory` section without crashes. The only issue I failed to fix/workaround is filed as #2077 PR checklist: - [x] `make` succeeds (on *nix) - [x] `make reftests` succeeds - [x] tested examples with the following backends: metal Co-authored-by: Dzmitry Malyshau <[email protected]>
|
I don't think this is actionable - we'll encode this limitation in the portability spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Metal requires the buffer strides to be multiple of 4, while Vulkan does not. There are quite a few failing tests inside "dEQP-VK.memory.*" that depend on that.
The text was updated successfully, but these errors were encountered: