<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 - Derive TTI instruction costs from scheduling models"
   href="https://bugs.llvm.org/show_bug.cgi?id=36550">36550</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Derive TTI instruction costs from scheduling models
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>libraries
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>trunk
          </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>Target Description Classes
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedbugs@nondot.org
          </td>
        </tr>

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

        <tr>
          <th>CC</th>
          <td>a.bataev@hotmail.com, andrea.dibiagio@gmail.com, atrick@apple.com, craig.topper@gmail.com, Florian.Hahn@arm.com, hfinkel@anl.gov, llvm-bugs@lists.llvm.org, spatel+llvm@rotateright.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>As discussed on D43769, we have a very divergent concept of costs between the
different cost models that we use for each target (TTI, scheduling etc.).

It would be very useful to investigate whether we can begin replacing all these
costs tables with values obtained directly from the target scheduling models,
and begin standardizing their usage so that we can use them in more areas than
just vectorization.

This will probably require a target to have models covering most/all of the CPU
types to avoid us, which is why Florian suggested that AArch64 be used for
initial experimentation.</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>