<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:mathieu.desnoyers@efficios.com" title="Mathieu Desnoyers <mathieu.desnoyers@efficios.com>"> <span class="fn">Mathieu Desnoyers</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_REOPENED "
   title="REOPENED --- - clang 3.3 and more recent miscompiles NULL pointer arithmetic in optimized builds (O2)"
   href="http://llvm.org/bugs/show_bug.cgi?id=18095">bug 18095</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;">Status</td>
           <td>RESOLVED
           </td>
           <td>REOPENED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>INVALID
           </td>
           <td>---
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_REOPENED "
   title="REOPENED --- - clang 3.3 and more recent miscompiles NULL pointer arithmetic in optimized builds (O2)"
   href="http://llvm.org/bugs/show_bug.cgi?id=18095#c3">Comment # 3</a>
              on <a class="bz_bug_link 
          bz_status_REOPENED "
   title="REOPENED --- - clang 3.3 and more recent miscompiles NULL pointer arithmetic in optimized builds (O2)"
   href="http://llvm.org/bugs/show_bug.cgi?id=18095">bug 18095</a>
              from <span class="vcard"><a class="email" href="mailto:mathieu.desnoyers@efficios.com" title="Mathieu Desnoyers <mathieu.desnoyers@efficios.com>"> <span class="fn">Mathieu Desnoyers</span></a>
</span></b>
        <pre>Have you guys considered perhaps emitting a warning when clang finds such an
undefined behavior ? This would have the advantage of both carrying the
optimization when undefined behaviors are detected (performance) and making
sure existing code that worked fine on gcc and previous llvm versions don't end
up crashing in front of application end-users without warning to the developer
(robustness).

Thanks for the pointers,

Mathieu</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>