<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> <span class="fn">Tapani Pälli</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - valgrind invalid reads when spilling"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110825">bug 110825</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>FIXED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - valgrind invalid reads when spilling"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110825#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - valgrind invalid reads when spilling"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110825">bug 110825</a>
              from <span class="vcard"><a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> <span class="fn">Tapani Pälli</span></a>
</span></b>
        <pre>commit a84de3fb7c1198f7cbd3b20a4231c14a7010f97f
Author: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>>
Date:   Mon Jun 3 17:09:12 2019 -0500

    intel/fs: Skip registers faster when setting spill costs

    This might be slightly faster since we're doing one read rather than
    two before we decide to skip.  The more important reason, however, is
    because no_spill prevents us from re-spilling spill registers.  In the
    new world in which we don't re-calculate liveness every spill, we may
    not have valid liveness for spill registers so we shouldn't even look
    their live ranges up.

    Bugzilla: <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - valgrind invalid reads when spilling"
   href="show_bug.cgi?id=110825">https://bugs.freedesktop.org/show_bug.cgi?id=110825</a>
    Fixes: e99081e76d4 "intel/fs/ra: Spill without destroying the..."
    Reviewed-by: Caio Marcelo de Oliveira Filho <<a href="mailto:caio.oliveira@intel.com">caio.oliveira@intel.com</a>>
    Tested-by: Tapani Pälli <<a href="mailto:tapani.palli@intel.com">tapani.palli@intel.com</a>></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>