<html>
    <head>
      <base href="https://llvm.org/bugs/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:sroland@vmware.com" title="sroland@vmware.com">sroland@vmware.com</a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Mesa llvmpipe piglit gl-3.2-layered-rendering-gl-layer regression"
   href="https://llvm.org/bugs/show_bug.cgi?id=23424">bug 23424</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;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>INVALID
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Mesa llvmpipe piglit gl-3.2-layered-rendering-gl-layer regression"
   href="https://llvm.org/bugs/show_bug.cgi?id=23424#c3">Comment # 3</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Mesa llvmpipe piglit gl-3.2-layered-rendering-gl-layer regression"
   href="https://llvm.org/bugs/show_bug.cgi?id=23424">bug 23424</a>
              from <span class="vcard"><a class="email" href="mailto:sroland@vmware.com" title="sroland@vmware.com">sroland@vmware.com</a>
</span></b>
        <pre>Ahh this is indeed a bug in mesa with an out-of-bounds index, I'll fix that.

It did not show up in the IR because whenever we dump the IR the out-of-bound
index is already optimized away... At least I don't know of any way to dump the
"raw" IR (we just do a LLVMDumpValue() on the function) which is actually
something I missed before :-(.

(It did show up as a difference to the old IR though, previously it was saying
  %0 = insertelement <4 x i32> undef, i32 %num_prims, i32 0
  %1 = shufflevector <4 x i32> %0, <4 x i32> undef, <4 x i32> zeroinitializer
  %2 = icmp sgt <4 x i32> %1, <i32 0, i32 1, i32 2, i32 3>

whereas now it was
  %0 = insertelement <4 x i32> undef, i32 %num_prims, i32 0
  %1 = shufflevector <4 x i32> %0, <4 x i32> undef, <4 x i32> zeroinitializer
  %2 = icmp sgt <4 x i32> %1, undef
)
That 0/1/2/3 vec4 was initialized with elements/indices ranging from 0-4
before.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>