Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Nov 14, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

This turned into a bigger change than just fixing the typo.
With the typo fixed, a bunch of tests started failing.
One issue in particular is that out of bounds `textureLoad`
needs to take swizzle into account since its allowed to
return any value inside the texture. I'm making the assuption
that the spec would say it can return any swizzled value in
the texture.

This comes up with depth textures because if texture-component-swizzle
is enabled then we check RGBA for depth textures instead of just R
and we expcet GBA to be 001. Before this change, if the texel address
was invalid we'd get a texel from the software texture and GBA would
be wrong and so no texels would match.

Theoretically, with this change, the software sampler code supports
swizzles but, that path is not really be exercised. Only the fact that
depth textures go from R??? to R001 is used.
`dpdxFine`, `dpdyFine`, and `fwidthFine` are not supported in
compatibility mode.
@pull pull bot locked and limited conversation to collaborators Nov 14, 2025
@pull pull bot added the ⤵️ pull label Nov 14, 2025
@pull pull bot merged commit 5a1dcdc into mozilla:main Nov 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant