<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [llvm-mca] Add a reporting view suitable for schedule model testing"
   href="https://bugs.llvm.org/show_bug.cgi?id=36874">36874</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[llvm-mca] Add a reporting view suitable for schedule model testing
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>new-bugs
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Windows NT
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>new bugs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>andrea.dibiagio@gmail.com
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>llvm-dev@redking.me.uk
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>craig.topper@gmail.com, greg.bedwell@sony.com, llvm-bugs@lists.llvm.org, spatel+llvm@rotateright.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>I've added some pipe/resource tests for btver2 (Jaguar) at
llvm\test\tools\llvm-mca\X86\BtVer2\resources-*.s

The issue is that at the moment the resource pressure view is trying to
determine the likely pipe each instruction will go down based on the previous
instructions. 

But for these style of tests we'd ideally shows the 'pressure' based purely on
that instruction in question - so each resource would have num_cycles / chance
of using that resource (similar to the lat:rthroughput view on llc 
-print-schedule</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>