<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - glScissor doesn't work with Mesa 9.2 on Intel GPUs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72586#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - glScissor doesn't work with Mesa 9.2 on Intel GPUs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72586">bug 72586</a>
from <span class="vcard"><a class="email" href="mailto:bk@f-m.fm" title="Branimir Karadzic <bk@f-m.fm>"> <span class="fn">Branimir Karadzic</span></a>
</span></b>
<pre>Last night at SteamDevDays I was talking with devs, someone mentioned that it
might be related to glBlitFramebuffer. I just tested it on SandyBridge and
disabling scissor right before blit fixes it. I also checked specs here
<a href="https://www.opengl.org/registry/specs/EXT/framebuffer_blit.txt">https://www.opengl.org/registry/specs/EXT/framebuffer_blit.txt</a> also mentions
it's correct:
The pixel copy bypasses the fragment pipeline. The only fragment
operations which affect the blit are the pixel ownership test and
the scissor test.
I think it's bug completely on my side, so you can resolve this as not a bug.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>