<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [regression, bisected] spec.arb_tessellation_shader.compiler.barrier-switch-always.tesc"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=94297">bug 94297</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Priority</td>
           <td>medium
           </td>
           <td>low
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [regression, bisected] spec.arb_tessellation_shader.compiler.barrier-switch-always.tesc"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=94297#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [regression, bisected] spec.arb_tessellation_shader.compiler.barrier-switch-always.tesc"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=94297">bug 94297</a>
              from <span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span></b>
        <pre>Although this is technically a regression, I don't really consider it critical.

The problem is that the GLSL compiler checks for barrier being in an allowed
position too late.  We passed this test previously because our switch
statements always generated lousy code (pointless loops that ran for a single
iteration). Now, we don't.

Also, the result of this bug is that we accept programs that we should reject
according to the rules.  We also happen to compile them and do what the author
intended.  So it's a portability problem (apps written against our driver may
work on our driver but not work on other drivers), but not going to break any
valid apps.</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>