Skip to content

Conversation

@jespertheend
Copy link
Contributor

@jespertheend jespertheend commented Dec 3, 2020

Fixes #693.


Preview | Diff

@jespertheend
Copy link
Contributor Author

Hmm, do I need IE status for these checks to pass? I have filled out the Invited Expert application form, but I'm not sure if this is necessary.

Copy link
Contributor

@kvark kvark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR!
There is a few things I believe need fixing, overall looks good!

spec/index.bs Outdated
<tr><td><dfn>maxVertexAttributes</dfn>
<td>{{GPUSize32}} <td>Higher <td>16
<tr class=row-continuation><td colspan=4>
The maximum number of {{GPUVertexBufferLayoutDescriptor/attributes}} when creating a {{GPURenderPipeline}}.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should say "in total across {{GPUVertexStateDescriptor/vertexBuffers}}" somewhere

spec/index.bs Outdated

1. |descriptor|.{{GPUVertexBufferLayoutDescriptor/attributes}}.length is less than or equal to 16.
1. |descriptor|.{{GPUVertexBufferLayoutDescriptor/arrayStride}} is less then or equal to 2048.
1. |descriptor|.{{GPUVertexBufferLayoutDescriptor/attributes}}.length is less than or equal to {{GPULimits/maxVertexAttributes}}.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this check should be replaced by a combined check over the whole pipeline (as opposed to a single vertex buffer)

unsigned long maxUniformBuffersPerShaderStage = 12;
unsigned long maxVertexBuffers = 8;
unsigned long maxVertexAttributes = 16;
unsigned long maxVertexArrayStride = 2048;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if maxVertexArrayStride is the name we want, but the editors can follow-up on that separately, no need to block this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I create a new issue for this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can file an issue during the Monday editing meeting if we don't immediately decide on something.

@kainino0x
Copy link
Contributor

Hmm, do I need IE status for these checks to pass? I have filled out the Invited Expert application form, but I'm not sure if this is necessary.

The ipr pass doesn't have to check for us to land this (it's non-required). That said, I think we could safely mark this contribution as non-substantive.

@kainino0x
Copy link
Contributor

Adding label for the limit name

Copy link
Contributor

@kainino0x kainino0x left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No additional comments :)

@w3cbot
Copy link

w3cbot commented Dec 4, 2020

jespertheend marked as non substantive for IPR from ash-nazg.

@kvark kvark requested a review from kainino0x December 5, 2020 00:39
@kainino0x kainino0x merged commit b5c36e3 into gpuweb:main Dec 5, 2020
bors bot added a commit to gfx-rs/wgpu that referenced this pull request Mar 2, 2021
1241: Update Extent3d::depth and Limits to latest upstream r=grovesNL a=kvark

**Connections**
- gpuweb/gpuweb#1390
- gpuweb/gpuweb#1328
- gpuweb/gpuweb#1163
- gpuweb/gpuweb#1274

**Description**
Just an API update up to spec.

**Testing**
Tested on wgpu-rs examples

Co-authored-by: Dzmitry Malyshau <[email protected]>
ben-clayton pushed a commit to ben-clayton/gpuweb that referenced this pull request Sep 6, 2022
This PR adds unimplemented stub tests for the `atomicStore` builtin.

Issue gpuweb#1274
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Figure out the base vertex input limits

4 participants