search for: memoryprofiler

Hi, Himanshu. I once wrote an LLVM IR-based memory profiling pass. Basically, I followed the code for EdgeProfiling. The source code is enclosed here, which worked with LLVM 2.8. Hope it is helpful. MemoryProfiling.cpp---the instrumentation pass, which inserts profiling function calls into the original program MemoryProfiling.c---the profiling library containing the profiling calls

Hey John, Thank you for the detailed reply. I tried to figure out myself which IR should I use for my purpose ( Clang's Abstract Syntax Tree (AST) or LLVM's SSA Intermediate Representation (IR). ), but couldn't really figure out which one to use. Here is what I m trying to do. Given any C/C++ program (like the one given below), I am trying to insert calls to some function, before and

I just read that LLVM project could be used to do static analysis on C/C++ codes using the analyzer Clang which the front end of LLVM. I wanted to know if it is possible to extract all the accesses to memory(variables, local as well as global) in the source code using LLVM. Is there any inbuilt library present in LLVM which I could use to extract this information. If not please suggest me how to

Hey Xiaoming, Thanks for those source codes. Can you please explain what this llvm-memory-profiling.patch does ? Thanks, Himanshu On Wed, Sep 28, 2011 at 6:49 AM, xiaoming gu <xiaoming.gu at gmail.com> wrote: > Hi, Himanshu. I once wrote an LLVM IR-based memory profiling > pass. Basically, I followed the code for EdgeProfiling. The source code is > enclosed here, which worked

The patch file is a diff file generated by "svn diff". It is about other modifications such as adding some lines to make files to make the added .c and .cpp files compiled. You may apply the patch file to LLVM source code by using a "patch" command or make the changes manually by reading the patch file. Xiaoming On Wed, Sep 28, 2011 at 6:05 AM, Himanshu Shekhar

Hey guys, I have seen your interesting conversion. I am new for LLVM as well as clang compiler. I am going to use it now. it is quite difficult when someone starts it from scratch. But it is enjoyable and it is possible to familiarize with the environment by short time. Am gonna to use clang + llvm to generate AST from source code by using clang and to do high level transformation. Then I want to

Hello, What you're describing is basically the parsing and codegen portions of clang. I'd suggest reading through the code there and posting to clang-dev if you have any specific questions. The clang devs are more likely to see your questions there as not all of them also hang out here. Regards, Jim On Sep 28, 2011, at 8:28 PM, eyasu getahun <eya.get at gmail.com> wrote: >

hello list! i seem to have a serious memory leak in my rails app that i run with a bunch of mongrels on windows (as services). i tried the MemoryProfiler i found at http://scottstuff.net/blog/articles/2006/08/17/memory-leak-profiling-with-rails but honestly i have no idea on how to read those string dumps. i tried diffing them but nothing there made any sense to me. any tips or hints would be greatly appreciated! best regards Ralf

Hello guys, I am trying to know how clang generates AST from source code. But it is not clear for me how clang generates it. Can you tell me which class or function of clang is building/generating AST? I want to see the specific function or algorithm of clang which generates AST. Thanks in advance for your idea. On Thu, Sep 29, 2011 at 1:22 PM, Jim Grosbach <grosbach at apple.com> wrote:

...'m still a relative n00b to Rails, and not sure how to go about fixing them. When I look in the dev/production logs, I don''t see any obvious errors in my code, so what else causes them? Are there some common errors/practices in general that will cause them? I also ran Scott Lairds MemoryProfiler.rb class (http://scottstuff.net/blog/articles/2006/08/17/memory-leak-profiling-with-rails) but have no idea what the outputted logs from it mean. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed...