Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Handle negative index in vertex processing#5076

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
kainino0x wants to merge1 commit intogpuweb:main
base:main
Choose a base branch
Loading
fromkainino0x:handle-negative-index

Conversation

@kainino0x
Copy link
Contributor

Also refactor the prose slightly so that this change makes more sense in context.

Fixes#5064

Also refactor the prose slightly so that this change makes more sense incontext.Fixes 5064
@kainino0xkainino0x added copyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.) apiWebGPU API labelsFeb 19, 2025
@kainino0xkainino0x added this to theMilestone 1 milestoneFeb 19, 2025
@kainino0xkainino0x requested a review fromtojiFebruary 19, 2025 19:59
@github-actions
Copy link
Contributor

@kainino0x
Copy link
ContributorAuthor

Oh, Brandon is out. Jim, could you review?

Copy link

@mwyrzykowskimwyrzykowski left a comment
edited
Loading

Choose a reason for hiding this comment

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

Doesn't the definition ofvertexElementRelativeOffset still allow for negativevertexElementIndex? E.g., consider

|vertexElementIndex| * |vertexBufferLayout|.{{GPUVertexBufferLayout/arrayStride}} +                |attributeDesc|.{{GPUVertexAttribute/offset}}.

as long as|attributeDesc|.{{GPUVertexAttribute/offset}} >=-|vertexElementIndex| * |vertexBufferLayout|.{{GPUVertexBufferLayout/arrayStride}} then as written I believevertexElementIndex < 0 would still be allowed.

Is negativevertexElementIndex supported across all APIs? I could only find reference in the GL specification which says it is not. Specifically I would wonder which values are populated invertex_index on the shader side.

@KangzKangz modified the milestones:Milestone 1,Milestone 2Oct 2, 2025
@Kangz
Copy link
Contributor

Is this PR still current?

@kainino0x
Copy link
ContributorAuthor

We never fixed this so yes. But I'll have to revisit at some point to figure out what we were doing.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@mwyrzykowskimwyrzykowskimwyrzykowski left review comments

@tojitojiAwaiting requested review from toji

@jimblandyjimblandyAwaiting requested review from jimblandy

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

apiWebGPU APIcopyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)

Projects

None yet

Milestone

Milestone 2

Development

Successfully merging this pull request may close these issues.

[WebGPU] Index resolution is potentially underspecified

3 participants

@kainino0x@Kangz@mwyrzykowski

[8]ページ先頭

©2009-2025 Movatter.jp