search for: heapprofil

Is anybody using the google heap profiler to analyze clang/llvm ?? http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html If so, do you know how to modify the build scripts to enable that. Tia. Reed

...Chandler Carruth wrote: > On Fri, Nov 11, 2011 at 11:36 AM, reed kotler <rkotler at mips.com > <mailto:rkotler at mips.com>> wrote: > > Is anybody using the google heap profiler to analyze clang/llvm ?? > > http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html > > If so, do you know how to modify the build scripts to enable that. > > Tia. > > > I have tried to use this in the past without terribly much success. > Instead, I usually use Valgrind to analyze the allocation patterns: > http://valgrind.org/docs/manua...

On Fri, Nov 11, 2011 at 11:36 AM, reed kotler <rkotler at mips.com> wrote: > Is anybody using the google heap profiler to analyze clang/llvm ?? > > http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html > > If so, do you know how to modify the build scripts to enable that. > > Tia. I have tried to use this in the past without terribly much success. Instead, I usually use Valgrind to analyze the allocation patterns: http://valgrind.org/docs/manual/ms-manual.html -------------- n...

...** > On 11/11/2011 11:39 AM, Chandler Carruth wrote: > > On Fri, Nov 11, 2011 at 11:36 AM, reed kotler <rkotler at mips.com> wrote: > >> Is anybody using the google heap profiler to analyze clang/llvm ?? >> >> http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html >> >> If so, do you know how to modify the build scripts to enable that. >> >> Tia. > > > I have tried to use this in the past without terribly much success. > Instead, I usually use Valgrind to analyze the allocation patterns: > http://valgrind.org/doc...

...tions, including the stack at each allocation, and information such as the allocation size and other statistics. I have implemented a prototype built using a stripped down and modified version of ASAN, however this will be a separate library utilizing sanitizer_common components. Compiler A simple HeapProfiler instrumentation pass instruments interesting memory accesses (loads, stores, atomics), with a simple load, increment, store of the associated shadow memory location (computed via a mask and shift to do the mapping of 64 bytes to 8 byte shadow, and add of the shadow offset). The handling is very s...

...each allocation, and information such > as the allocation size and other statistics. I have implemented a prototype > built using a stripped down and modified version of ASAN, however this will > be a separate library utilizing sanitizer_common components. > Compiler > > A simple HeapProfiler instrumentation pass instruments interesting memory > accesses (loads, stores, atomics), with a simple load, increment, store of > the associated shadow memory location (computed via a mask and shift to do > the mapping of 64 bytes to 8 byte shadow, and add of the shadow offset). > Th...

...nformation > such as the allocation size and other statistics. I have implemented a > prototype built using a stripped down and modified version of ASAN, > however this will be a separate library utilizing sanitizer_common > components. > > > Compiler > > A simple HeapProfiler instrumentation pass instruments interesting > memory accesses (loads, stores, atomics), with a simple load, > increment, store of the associated shadow memory location (computed > via a mask and shift to do the mapping of 64 bytes to 8 byte shadow, > and add of the shadow offset)...

...formation such >> as the allocation size and other statistics. I have implemented a prototype >> built using a stripped down and modified version of ASAN, however this will >> be a separate library utilizing sanitizer_common components. >> Compiler >> >> A simple HeapProfiler instrumentation pass instruments interesting memory >> accesses (loads, stores, atomics), with a simple load, increment, store of >> the associated shadow memory location (computed via a mask and shift to do >> the mapping of 64 bytes to 8 byte shadow, and add of the shadow offs...