<p dir="ltr">The resulting binary size is almost identical to the one that's dynamically linked.</p>
<div class="gmail_quote">On Jul 2, 2015 02:45, "Pavel Labath" <<a href="mailto:labath@google.com">labath@google.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D10858-23198371&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=MEqT8U_n7oNfuDW5NRbY3ZV384ZquXIYFPWmprwUdKM&m=ZOWDfY7qUrzSMFLGpVhnnY_GSnNo2cJauFHl_yZCBV0&s=BUqxRVCt3XsJbjWbbRsye50DLeoU6jtlVK2OIJyKH68&e=" rel="noreferrer" target="_blank">http://reviews.llvm.org/D10858#198371</a>, @tberghammer wrote:<br>
<br>
> You are linking statically against the system libraries (such as libc, libm, libdl) what might not be a portable solution if they are depending on features only present in some device / kernel.<br>
<br>
<br>
The platforms should be backward compatible. A binary which works on an older device (statically linked or not) should work on newer devices as well, so I don't anticipate problems of this sort. However, libc is pretty big, so the size question is valid imho.<br>
<br>
<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_D10858&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=MEqT8U_n7oNfuDW5NRbY3ZV384ZquXIYFPWmprwUdKM&m=ZOWDfY7qUrzSMFLGpVhnnY_GSnNo2cJauFHl_yZCBV0&s=t39OmmPzh0UnFkZ69DwVh9Uh-5jv3fpOU5M5tJTeJHI&e=" rel="noreferrer" target="_blank">http://reviews.llvm.org/D10858</a><br>
<br>
EMAIL PREFERENCES<br>
  <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__reviews.llvm.org_settings_panel_emailpreferences_&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=MEqT8U_n7oNfuDW5NRbY3ZV384ZquXIYFPWmprwUdKM&m=ZOWDfY7qUrzSMFLGpVhnnY_GSnNo2cJauFHl_yZCBV0&s=jLKO5Vguv1zZ7lZVklGpjBBWvrOWugTHDcKIlbHR_3o&e=" rel="noreferrer" target="_blank">http://reviews.llvm.org/settings/panel/emailpreferences/</a><br>
<br>
<br>
</blockquote></div>