Comment # 13
on bug 66067
from Roland Scheidegger
(In reply to comment #12) > (In reply to comment #11) > > > ARB_fragment_program_shadow may leave it undefined, but the GL spec ... > > > > Which spec exactly? GL specifications only cover GLSL shaders. > > ARB_fragment_program is separate from that and has its own rules. The > > extension specification clearly states that behaviour is undefined. > > > Section 8.23.1 of the GL 4.4 spec, which I paraphrased in comment #9. This only covers the DEPTH_TEXTURE_MODE but not the shadow target of arb_fragment_program_shadow. To quote from there: How should ARB_fragment_program_shadow function? a. Simply remove the interaction with ARB_shadow so that TEXTURE_COMPARE_MODE behaves exactly as specified in the OpenGL 1.4 specification. b. Add "SHADOW" targets to texture lookup instructions. TEXTURE_COMPARE_MODE is ignored. For samples from a SHADOW target TEXTURE_COMPARE_MODE is treated as COMPARE_R_TO_TEXTURE; otherwise, it is treated as NONE. c. Like (b), but with undefined results if TEXTURE_COMPARE_MODE and/or the internal format of the texture does not match the target. d. A hybrid of (a) and (b), where the SHADOW target means to use the TEXTURE_COMPARE_MODE state. RESOLVED - Option c, undefined behavior when the target and mode do not match. So if the cg compiler really does something as you suggested it is simply crazy to expect this to work. At least I see absolutely nothing why that GL wording somehow would apply to this (non-core) extension.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
