search for: dectector

...l differences in code, as opposed to differences in type/vtable layout, is going to be pretty fraught with uninteresting positives, but if you want to chase that rabbit, it's your time spent. Anyway, you only need to hash in function bodies for inline functions unless this is also an ELF abuse dectector. (*Whether* a function is inline seems like a legitimate thing to hash for the function signature.) John. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130715/63a47380/attachment.html>

On Mon, Jul 15, 2013 at 3:12 PM, John McCall <rjmccall at apple.com> wrote: > On Jul 11, 2013, at 6:13 PM, Nick Lewycky <nlewycky at google.com> wrote: > > On 11 July 2013 18:02, John McCall <rjmccall at apple.com> wrote: > >> On Jul 11, 2013, at 5:45 PM, Nick Lewycky <nlewycky at google.com> wrote: >> > Hi! A few of us over at Google think a

...ot, then we've learned something important...). For non-inline functions and classes, the checking would be more novel, so the uninteresting positive rate is hard to be sure about. > Anyway, you only need to hash in function bodies for inline functions > unless this is also an ELF abuse dectector. (*Whether* a function is > inline seems like a legitimate thing to hash for the function signature.) > Giving different definitions (for either functions or classes) in different source files is one of the things we'd like to catch (although there are probably more direct ways to do so...