search for: cmpimag

I like that idea! > On Jun 2, 2015, at 12:00 PM, Smith, Kevin B <kevin.b.smith at intel.com> wrote: > > The code for cmpimage and getdep consists of five source files, with the following sizes > > $ wc * > 5912 20353 191869 cmpimage.cpp > 290 1328 10668 elf.h > 1496 5006 41691 getdep.cpp > 233 959 7692 macho.h > 403 1831 18394 pecoff.h > 8334 29477 270314 total &gt...

...ance noise) > from our own performance tracking tools. > > We are willing to contribute the source code for this to the LLVM community if there is interest. > > There are two programs involved: getdep, which displays the list of DLL/.so dependencies of the image in question, and cmpimage itself, which does the comparison ignoring the parts not contributed by the compiler. The cmpimage program is also almost completely derived from the published object format descriptions. > > Let me know if there is interest in these pieces of tooling, and if so, what you think next steps...

...(and therefore some performance noise) from our own performance tracking tools. We are willing to contribute the source code for this to the LLVM community if there is interest. There are two programs involved: getdep, which displays the list of DLL/.so dependencies of the image in question, and cmpimage itself, which does the comparison ignoring the parts not contributed by the compiler. The cmpimage program is also almost completely derived from the published object format descriptions. Let me know if there is interest in these pieces of tooling, and if so, what you think next steps should be....

...(and therefore some performance noise) from our own performance tracking tools. We are willing to contribute the source code for this to the LLVM community if there is interest. There are two programs involved: getdep, which displays the list of DLL/.so dependencies of the image in question, and cmpimage itself, which does the comparison ignoring the parts not contributed by the compiler. The cmpimage program is also almost completely derived from the published object format descriptions. Let me know if there is interest in these pieces of tooling, and if so, what you think next steps should be....

...gt; > from our own performance tracking tools. > > We are willing to contribute the source code for this to the LLVM > community if there is interest. > > There are two programs involved: getdep, which displays the list of > DLL/.so dependencies of the image in question, and cmpimage itself, > which does the comparison ignoring the parts not contributed by the > compiler. The cmpimage program is also almost completely derived from > the published object format descriptions. > > Let me know if there is interest in these pieces of tooling, and if > so, wha...

On Thu, May 21, 2015 at 11:24 AM, Chris Matthews <chris.matthews at apple.com> wrote: > I agree this is a great idea. I think it needs to be fleshed out a little > though. > > It would still be wise to run the regression detection algorithm, because > the test suite changes and the machines change, and the algorithm is not > perfect yet. It would be a valuable source of

...from our own performance tracking tools. >> >> We are willing to contribute the source code for this to the LLVM community if there is interest. >> >> There are two programs involved: getdep, which displays the list of DLL/.so dependencies of the image in question, and cmpimage itself, which does the comparison ignoring the parts not contributed by the compiler. The cmpimage program is also almost completely derived from the published object format descriptions. >> >> Let me know if there is interest in these pieces of tooling, and if so, what you think ne...