Have you thought about force emitting the memcpy metadata that describes the padding holes in the struct, and use that to predicate the instrumentation?
While there is some risk that the optimizer loses this information, frankly, we want to find all those places and fix them. On Thu, Nov 6, 2014 at 8:01 PM, Kostya Serebryany <[email protected]> wrote: > Hi majnemer, rsmith, > > If we've added poisoned paddings to a type do not emit memcpy for > operator=. > > http://reviews.llvm.org/D6160 > > Files: > lib/CodeGen/CGExprCXX.cpp > test/CodeGen/sanitize-address-field-padding.cpp > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits > >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
