<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] Move the llvm-mca library into core llvm."
   href="https://bugs.llvm.org/show_bug.cgi?id=38731">38731</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[llvm-mca] Move the llvm-mca library into core llvm.
          </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>All
          </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>unassignedbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>matthew.davis@sony.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This is a bug to track the discussion and RFC (not yet created) for moving the
llvm-mca library into llvm/lib.

The goal of this feature is to make the core of llvm-mca available for use by
optimizations and other llvm components.   For example, using llvm-mca's core
as an aid for cost modeling.  As llvm-mca grows, other components of llvm can
benefit from the ability to simulate various stages of an instruction pipeline.

To accomplish this we'll need a RFC with well defined use cases.  This work
involves moving the tools/llvm-mca/include and tools/llvm-mca/lib
subdirectories of into llvm/include and llvm/lib accordingly.  Perhaps
llvm/lib/MCA and llvm/include/MCA.</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>