<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Trine 2's fragment normal buffer is mixtextured on Radeon HD 6770 (Juniper)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66067#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Trine 2's fragment normal buffer is mixtextured on Radeon HD 6770 (Juniper)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66067">bug 66067</a>
from <span class="vcard"><a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> <span class="fn">Roland Scheidegger</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=66067#c12">comment #12</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=66067#c11">comment #11</a>)
> > > 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 <a href="show_bug.cgi?id=66067#c9">comment #9</a>.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>