<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [gallium] glCopyPixels is affected by enabled texture state"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96943#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [gallium] glCopyPixels is affected by enabled texture state"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96943">bug 96943</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 Ilia Mirkin from <a href="show_bug.cgi?id=96943#c2">comment #2</a>)
<span class="quote">> (In reply to Roland Scheidegger from <a href="show_bug.cgi?id=96943#c1">comment #1</a>)
> > The piglit test is probably wrong (I didn't really look), at least different
> > results based on enabled texturing don't surprise me. This is one of the
> > more weird "features" of glCopyPixels(), glDrawPixels() and friends.
> > From the respective man pages:
> > "Texture mapping, fog, and all the fragment operations are applied before
> > the fragments are written to the frame buffer." So if you don't disable
> > texturing, you'll get texturing on top of your copied pixels (which just
> > represent the primary color), in whatever way the shader specified (albeit
> > the texture coords should be constant IIRC).
>
> OK, so in that case, any time that a texture unit is enabled, we should be
> falling back to the drawpixels-style shader? (The multiply, btw, is coming
> from the texture combine logic, which defaults to "combine" aka "multiply".)</span >
Technically I think yes. I don't know if the results are actually really
correct, though in any case (is it using the current tex coord etc.). And just
like this piglit test, I don't think any app ever expects this behavior - most
likely if they do this it's an app bug... So might just want to fix the piglit
test and pretend it's undefined behavior...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>