<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 - gc.relocate and gc.result should be marked readnone"
   href="https://bugs.llvm.org/show_bug.cgi?id=49607">49607</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>gc.relocate and gc.result should be marked readnone
          </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>Linux
          </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>Core LLVM classes
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>listmail@philipreames.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This bug exists to track work towards marking the intrinsics for gc.result and
gc.relocate as readnone.  Currently, there are marked as readonly in
Intrinsics.td.  I'd previously tried this under
<a href="https://reviews.llvm.org/D97974">https://reviews.llvm.org/D97974</a>, but we hit complications after commit and
needed to revert.  See the last comment on the review for details on the
fallout.  

My current plan is to stage changes in a manner which make it easy to test the
definition change by itself, ask for another round of testing with that change
enabled, and then back out any migration specific pieces.  The main purpose of
this bug is to have a bug number to reference from comments for the migration
specific pieces.</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>