similar to: [LLVMdev] google heap profile

Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] google heap profile"

2011 Nov 11
0
[LLVMdev] google heap profile
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.
2011 Nov 11
2
[LLVMdev] google heap profile
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
2011 Nov 11
0
[LLVMdev] google heap profile
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 ?? >> >>
2012 Jun 04
2
[LLVMdev] style guidelines
Probably this has come up before... but have we considered just adopting the Google style guidlines and maybe modifying it in some places? They have a nice script for c++ which will check for many things. http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py
2010 Jun 16
6
[LLVMdev] [patch] New feature: debug info in add2line format (--jit-emit-debug-addr2line)
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
2012 Jun 04
0
[LLVMdev] style guidelines
On Mon, Jun 4, 2012 at 2:29 PM, reed kotler <rkotler at mips.com> wrote: > Probably this has come up before... but have we considered just adopting > the Google style guidlines and maybe modifying it in some places? > Despite working at Google, and having to cope with multiple different styles in my day-to-day work as a consequence, I would not push for this. I think that we
2010 Jun 19
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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
2010 Jun 19
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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
2011 Oct 09
2
[LLVMdev] Comparison of optimizations
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
2011 Feb 10
3
how will CentOS handle the perftools 1.7 vs. 1.6 issue?
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]: >
2010 Jun 19
0
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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
2010 Dec 19
0
[LLVMdev] Why google-perftools fails to detect stack of JITted code? (with option -disable-fp-elim set)
I have this problem: google-perftools fails to detect stack for the code run under JIT called through C++ api from my program. It shows in profile like all program is one block with the name _init. I clearly do set the option NoFramePointerElim and I do see how it makes a difference in stack frame under gdb. When running some code in JIT in lli (with option -disable-fp-elim) google perftools
2010 Jun 18
2
[LLVMdev] Why google-perftools fails on the JITted code?
I am trying to run some code allocating a lot of memory and not releasing it in JIT under google-perftools. Just one function 'main' calling 'malloc'. google-perftools fails to correctly read stack when malloc is called from inside the JITted code, and as a result perftools report is wrong: address of 'main' procedure appears shifted 0x3946e1d0->0x3946e1ed and is
2010 Jun 22
2
[LLVMdev] [patch] New feature: debug info for function memory ranges (-jit-emit-debug-function-range)
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 >
2010 Jun 18
3
[LLVMdev] Why google-perftools fails on the JITted code?
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 >
2010 Jun 19
0
[LLVMdev] Why google-perftools fails on the JITted code?
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
2009 Aug 28
6
Google's R Style Guide
Perhaps most of you have already seen this? http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html Comments/Critiques? Thanks, Esmail ps: Reminds me of PEP 8 for Python http://www.python.org/dev/peps/pep-0008/ Maybe not that surprising since Python is also one of the main languages used by Google.
2020 Aug 24
2
MultiDatabase shard count limitations
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
2010 Mar 28
2
Possible improvements/clarifications for R-forge (Was: Re: Using SVN + SSH on windows)
Hi, first, r-forge.r-project.org is filling a need and provides a great service to the community. Please read this thread as sincere feedback for making it even better, not as a complaint. I fully understand that r-forge is ran by limited resources and on a volunteer basis. I'll list some points about r-forge that I think could be improved/clarified. Not expecting anything, just sharing my
2010 Mar 28
2
Setting up TortoiseSVN and PuTTY on Windows for r-forge.r-project.org (Was: Re: Using SVN + SSH on windows)
Here are some notes/observations I've done on my setup that works for me. Hopefully it will be added to some r-forge documentation/wiki. I use: Windows Vista Business SP2 32bit TortoiseSVN 1.6.7 (Build 18415 - 32 Bit , 2010/01/22 17:55:06) PuTTY v0.60 (with Pageant v0.60) I have a deprecated r-forge project ('r-oo') that I will use through out. My r-forge username is