<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Add support for jumping between MSVC inline asm blob labels"
   href="https://bugs.llvm.org/show_bug.cgi?id=24529">bug 24529</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;">Resolution</td>
           <td>---
           </td>
           <td>WONTFIX
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Add support for jumping between MSVC inline asm blob labels"
   href="https://bugs.llvm.org/show_bug.cgi?id=24529#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Add support for jumping between MSVC inline asm blob labels"
   href="https://bugs.llvm.org/show_bug.cgi?id=24529">bug 24529</a>
              from <span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span></b>
        <pre>I agree with everything in c#3. I'm pretty close to just marking this WONTFIX.

We *could* hypothetically implement this the way we implemented WinEH, where we
have an inline asm instrution that is both a terminator and a "leader", meaning
must be the first non-phi instruction like a landingpad or catchswitch. Such a
block has no insertion point: passes must non insert any non-phi instructions
into it. In theory, the existence of catchswitch requires that all passes
handle these blocks gracefully. Any phis appearing in a leader-terminator block
would be demoted to memory. This would ensure that no code is generated between
two asm blobs that should be consistent. We would also need to communicate that
the second block *must* be the layout successor, which is also pretty weird.

However, that's all quite challenging and probably not worth anyone's time.
Let's go with wontfix.</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>