similar to: sprof works on your Debian/Ubuntu ?

No matter how I try, I can't seem to get a library profile from sprof on CentOS5. Does anyone know if sprof actually works on CentOS5? I'd be very interested to hear if anyone is using it successfully. At the moment I'm trying something like this to get the dump: LD_LIBRARY_PATH=. LD_PROFILE=libmy.so ./mymain where libmy.so is the library I want to profile, and mymain is the

Hello, I got these errors during compile wine-20010629 in x86 Solaris make[2]: Leaving directory `/d1/wine-20010629/miscemu' gcc -o wine miscemu/miscemu.o -L./dlls -lntdll -L./library -lwine -L./unicode -lwine_unicode -lsocket -lnsl -lm make[1]: Entering directory `/d1/wine-20010629/debugger' gcc -c -I. -I. -I../include -I../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC

Hello, again. I'm interested to learn how programmers develop & test C/C++ code with R packages in Linux. I've been reading R source and the manual on Writing R Extensions but there are just a couple of details I can't understand. I wish I could watch over a developer's shoulder to see how people actually do this. I've tested a bit. I am able to take package.tar.gz

This new option will allow to output function information in the same format as addr2line from binutils emits: ... 0xABCDEF01 T function_name_is_here ... This feature is useful to profile the code when it is run in JIT by external tools like valgrind and google-perftools. For example, google-perftools runs addr2line on executable and uses the resulting file to resolve memory addresses to

This new option (--jit-emit-debug-function-range) will allow to output function information for memory ranges that functions occupy in memory while they run in JIT. File format generated is like this: ... 0x5000000 0x5001000 function_name_is_here ... This feature is useful for external tools like valgrind and google-perftools to profile the code when it is run in JIT. Particularly

Have you found http://llvm.org/docs/DebuggingJITedCode.html? The JIT already has support for something like this for gdb's benefit. Perftools and valgrind just don't know how to find it yet. On Sat, Jun 19, 2010 at 2:03 PM, Yuri <yuri at rawbw.com> wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that

In order to avoid a cross post, the following background quote is from SCIENTIFIC-LINUX-USERS at fnal.gov: <quote> On Wed, Feb 9, 2011 at 11:27 AM, Ewan Mac Mahon <ewan at macmahon.me.uk> wrote: > > I'm a little bit hazy on the details, but there are some slides from the > meeting here[1]: >

On 06/19/2010 14:14, Jeffrey Yasskin wrote: > Have you found http://llvm.org/docs/DebuggingJITedCode.html? The JIT > already has support for something like this for gdb's benefit Yes, I saw it and tried it. -jit-emit-debug generates ELF image in memory with debug info. Another option -jit-emit-debug-to-disk creates .o ELF files with debug info, one per function. If there are thousands

Hi, I am working on an R package which includes some C routines. I would like to profile the C routines (built with GCC under Debian Linux). I tried running R with LD_PROFILE=/path/to/C/library.so R and executing functions that would invoke the code therein. The code takes about twice as long to run with LD_PROFILE set than without, so I am guessing that profiling is taking place. However,

On 06/19/2010 14:03, Yuri wrote: > This new option (--jit-emit-debug-function-range) will allow to output > function information for memory ranges that functions occupy in memory > while they run in JIT. File format generated is like this: > ... > 0x5000000 0x5001000 function_name_is_here > ... > > This feature is useful for external tools like valgrind and >

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

On Jun 18, 2010, at 3:29 AM, Yuri wrote: > Now I see that JITted code doesn't have standard prolog, on x86 each > procedure instead begins with 'sub $0x4,%esp'. > > Is there an option to make JIT generate regular prologs? Try turning off frame pointer elimination. On the llc command line, this is -disable-fp-elim -Chris > > Yuri >

On Sat, Jun 19, 2010 at 4:35 AM, Chris Lattner <clattner at apple.com> wrote: > > On Jun 18, 2010, at 3:29 AM, Yuri wrote: > >> Now I see that JITted code doesn't have standard prolog, on x86 each >> procedure instead begins with 'sub    $0x4,%esp'. >> >> Is there an option to make JIT generate regular prologs? > > Try turning off frame

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 > <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

Hi, I want to measure the performance of functions within a program, in order to see whether or not a given set of optimizations are useful (making the code faster in my case). It would be ideal to compare the LLVM IR representation of the functions before and after the optimizations, but the process has to be automatized so if there is no code that can do this now then I guess it will be too

Olly Betts <olly at survex.com> wrote: > The report you show seems to be just the time take by each function > directly rather than including functions it calls. It looks like a lot > of the time is spent in cursor movement, as totalling up things that > seem like they'd be due to that I quickly get to 40+% but it's hard > to tell if that's about the actual total

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.

On Fri, Nov 11, 2011 at 11:45 AM, reed kotler <rkotler at mips.com> wrote: > ** > 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 ?? >> >>

Hi, This is a proposed fix for bug 16847 [1]. It is essentially the patch provided by Martin Nowack in the bug report but I have added a test case and an ifdef macro around the modified code in Process::GetMallocUsage() The issue seems to be that the ptmalloc2 allocator used in glibc (in my case 2.19) does not include mmap()'ed memory in mallinfo.uordblks and so mallinfo.hblkhd needs to be

I'm working up a set of small working examples in R to show what various distributions are and the beauty of the central limit theorem. Those example programs are in this directory: http://lark.cc.ukans.edu/~pauljohn/R/ExampleCode/ You can feel free to use those if you want, or you can send me other small working example code for R. The key here is small, self contained things that