<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:rengolin@gmail.com" title="Renato Golin <rengolin@gmail.com>"> <span class="fn">Renato Golin</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - [Arm32] Atomic operations on 64-bit operations have invalid bit-cast"
   href="https://bugs.llvm.org/show_bug.cgi?id=50721">bug 50721</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 - [Arm32] Atomic operations on 64-bit operations have invalid bit-cast"
   href="https://bugs.llvm.org/show_bug.cgi?id=50721#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - [Arm32] Atomic operations on 64-bit operations have invalid bit-cast"
   href="https://bugs.llvm.org/show_bug.cgi?id=50721">bug 50721</a>
              from <span class="vcard"><a class="email" href="mailto:rengolin@gmail.com" title="Renato Golin <rengolin@gmail.com>"> <span class="fn">Renato Golin</span></a>
</span></b>
        <pre>Looking at other back-ends, all of them create bitcasts to
`Builder.getInt8PtrTy()` which assumes whatever pointer was already in the
default address space. None of them have guards or asserts to check the address
space.

Of course, some of that code is from before address spaces were introduced, but
what I mean is that, since it has been added (many years ago), none of them had
to deal with different address spaces at that level, which means the
expectation David mentioned is pervasive and historical.

I don't think we need any special treatment of bitcasts in the ARM back-end. If
there's anything that needs to be encoded, it should be at a higher level.</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>