On 2025-04-24 07:13, Iago Toral wrote:
> For v3d yzw would be 0,0,1.
>
It's worth noting that in our framebuffer fetch implementation we
override unused components with undefs.
Ella
> Iago
>
> El mié, 23-04-2025 a las 12:24 -0400, Mike Blumenkrantz escribió:
>> Hi,
>>
>> An issue recently cam
For v3d yzw would be 0,0,1.
Iago
El mié, 23-04-2025 a las 12:24 -0400, Mike Blumenkrantz escribió:
> Hi,
>
> An issue recently came up in the GL working group: what is the
> robustness behavior of framebuffer fetch? For example, if a
> framebuffer attachment format is R8_UNORM, what are the YZW
NVIDIA is a texelFetch, so (x, 0, 0, 1)
Intel is a TexelFetch pre-SKL. I'm not sure what it is for SKL+. Probably
(x, 0, 0, 1) but it's been a while.
~Faith
On Wed, Apr 23, 2025 at 1:11 PM Marek Olšák wrote:
> AMD lowers it to an image load, which follows the rules for image views,
> so (x, 0
AMD lowers it to an image load, which follows the rules for image views, so
(x, 0, 0, 1) for R8_UNORM.
Marek
On Wed, Apr 23, 2025 at 12:25 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> Hi,
>
> An issue recently came up in the GL working group: what is the robustness
> behavior
Hi,
An issue recently came up in the GL working group: what is the robustness
behavior of framebuffer fetch? For example, if a framebuffer attachment
format is R8_UNORM, what are the YZW components which get read back?
If people from all the drivers (besides panfrost) which support this
extension
