[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 Timothy Arceri changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #18 from Timothy Arceri --- Fix tested and sent to list: https://patchwork.freedesktop.org/patch/150080/ New piglit test: https://patchwork.freedesktop.org/patch/150079/ -- You are receiving this mail because: You are the assigne

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #17 from Timothy Arceri --- Created attachment 128306 --> https://bugs.freedesktop.org/attachment.cgi?id=128306&action=edit Validate sampler types across the whole program It's untested but this patch should do the trick. Note it

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #16 from Marek Olšák --- Workaround for radeonsi: CI-VI: If the resource type and instruction mismatch (e.g. a buffer constant with an image instruction, or an image resource with a buffer instruction), the instruction will be ignore

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #15 from Timothy Arceri --- (In reply to Nicolai Hähnle from comment #10) > I can reproduce this now. It really seems like this should be fixed in Mesa > main, though: there is already code that checks for this condition when it > aff

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #14 from Matias N. Goldberg --- Dang it! You're right. I forgot GL allows (requires?) changing sampler values after the shader is compiled. As for glValidateProgram, our actual software (not this sample) would often warn about sampl

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #13 from Roland Scheidegger --- (In reply to Matias N. Goldberg from comment #12) > I believe the error should happen in either glLinkProgram or glUseProgram, > and then every time glDraw* is called. This is impossible, since the valu

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #12 from Matias N. Goldberg --- I believe the error should happen in either glLinkProgram or glUseProgram, and then every time glDraw* is called. If I recall correctly AMD's Windows driver raised the error every time glDrawArrays was

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 --- Comment #11 from Tapani Pälli --- > All other GPU drivers I tested with handle this gracefully by raising a > GL_INVALID_OPERATION error and continuing rendering the rest normally. For which command in the sample program should GL_INVALID_OP

[Mesa-dev] [Bug 97524] Samplers referring to the same texture unit with different types should raise GL_INVALID_OPERATION

https://bugs.freedesktop.org/show_bug.cgi?id=97524 Nicolai Hähnle changed: What|Removed |Added Summary|Invalid sampler settings|Samplers referring to the