<div dir="ltr">Have you thought about force emitting the memcpy metadata that describes the padding holes in the struct, and use that to predicate the instrumentation?<div><br></div><div>While there is some risk that the optimizer loses this information, frankly, we want to find all those places and fix them.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 6, 2014 at 8:01 PM, Kostya Serebryany <span dir="ltr"><<a href="mailto:kcc@google.com" target="_blank">kcc@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi majnemer, rsmith,<br>
<br>
If we've added poisoned paddings to a type do not emit memcpy for operator=.<br>
<br>
<a href="http://reviews.llvm.org/D6160" target="_blank">http://reviews.llvm.org/D6160</a><br>
<br>
Files:<br>
  lib/CodeGen/CGExprCXX.cpp<br>
  test/CodeGen/sanitize-address-field-padding.cpp<br>
<br>_______________________________________________<br>
cfe-commits mailing list<br>
<a href="mailto:cfe-commits@cs.uiuc.edu">cfe-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits</a><br>
<br></blockquote></div><br></div>