similar to: [LLVMdev] Profiling - execution count of basic blocks...

Hello. I'm using these commands to compile the code below in order to collect edge/blocks profiling: clang -emit-llvm -c sort.c -o sort.bc opt -insert-edge-profiling sort.bc -o sort_prof.bc clang sort_prof.bc -lprofile_rt -L/llvms/lib -o sort_prof then I run the program and display the profiling information using llvm-prof sort_prof.bc, and the result is:

Hi members, I am a LLVM newbee. I am working in path profiling. I got an error message when reading the path profile data I made a sample source named foo.c The command chain to make llvm path profiling as follows: 1. Compile to LLVM Bitcode llvm-gcc –emit-llvm foo.c –c –o foo.bc 2. Insert Path Instruments opt –insert-path-profiling foo.bc –o foo_path.bc 3. Link with profile

Hi, I am new to LLVM, and would like to write a dynamic profiler, say which prints out the load address of all the load instructions encountered in a program. >From what I could pick up, edge-profiler.cpp increments a counter dynamically which is somehow dumped onto llvmprof.out by profile.pl Could anyone explain me how this works? Can I instrument the code to dump out the load addresses or

Dear all, I have already checked some related posted messages, such as: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/012315.html and http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-February/012466.html After getting rid of some error messages, I was able to run the following commands: 1) opt -insert-path-profiling matmul.bc -o matmul.pp.bc 2) lli -load

Hello, See answers below On 31/01/13 00:23, César wrote: > Hello. > > I'm using these commands to compile the code below in order to collect > edge/blocks profiling: > > clang -emit-llvm -c sort.c -o sort.bc > opt -insert-edge-profiling sort.bc -o sort_prof.bc > clang sort_prof.bc -lprofile_rt -L/llvms/lib -o sort_prof > > then I run the program and display the

What version of LLVM are you using? The profiling framework is completely messed up in the newer versions of LLVM.. I used to work with profiling in 2.5 some time ago, and it seemed to work fine.. If you really need this to work quickly, you might want to just get the old version and get on with it.. The newer versions of LLVM need to get the profiling part fixed soon..It is messing up my work as

Hello everybody, I am a beginner in LLVM and need to know how to use LLVM to instrument a C program and execute this instrumented program with different test cases to determine the branch coverage information for each test case. Any suggestion or help is more than welcomed. Thanks in advance. Ahmed Raafat. -- View this message in context:

Hi Ahmed! Adventure wrote: > Hello everybody, I am a beginner in LLVM and need to know how to use > LLVM to instrument a C program and execute this instrumented program > with different test cases to determine the branch coverage information > for each test case. Any suggestion or help is more than welcomed. Thanks > in advance. Ahmed Raafat. (In the following instructions you

Hi Daniel! Daniel Dunbar wrote: > I merged in my changes to your patch, which results in the attached > patch. There may be some missed merge errors. The main problem I have > with the rest of this patch is that it causes a regression in > llvm-prof's behavior. I tried running edge profiling on the > MultiSource/Applications/aha benchmark in the llvm test-suite, and >

Hi the list, I am writing a package in S4 and I do not manage to understand a bug. The "R CMD check" and the "R CMD build" both work. Here is links to the package (not on CRAN yet for the raison that I explain bellow): http://christophe.genolini.free.fr/aTelecharger/kml_0.5.zip http://christophe.genolini.free.fr/aTelecharger/kml_0.5.tar.gz Then I install the package and I

Hello, I am planning on contributing path profiling to LLVM by the end of August. I have written a document of what the interface to the path profiles would look like at that time. If someone has any amendments, I can incorporate them. http://www.cs.ualberta.ca/~pejic/PathProfiling.html Slobodan Pejic

Good Morning. On 22.07.09 14:47), Andreas Neustifter wrote: > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a regression in >> llvm-prof's behavior. I tried running edge profiling on the >>

On Friday 10 July 2009 18:06, Slobodan Pejic wrote: > Hello, > > I am planning on contributing path profiling to LLVM by the end of > August. I have written a document of what the interface to the path > profiles would look like at that time. If someone has any amendments, I > can incorporate them. > > http://www.cs.ualberta.ca/~pejic/PathProfiling.html Slobodan, This

Sorry, forgot attachment. On 23.07.09 07:40), Andreas Neustifter wrote: > Good Morning. > > On 22.07.09 14:47), Andreas Neustifter wrote: >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached >>> patch. There may be some missed merge errors. The main problem I have >>> with the rest of this patch is that it

Hello, My name is Rantao Chen and i am a student at the University of Maryland. I am currently doing some research for a professor to do Basic Block profiling using LLVM. I have set up the environment correctly and built the profile_rt.so shared library, but i am having some problems using the LLVM profiling tools. I run "opt -insert-function-profiling -insert-block-profiling input.bc

Hi Andreas, Sorry for the lag time... On Wed, Jul 22, 2009 at 5:47 AM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: > Hi Daniel! > > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a

Hi! Daniel Dunbar wrote: > > Sorry for the lag time... No problem. As long as I know that you get to it sometime its fine for me... > On Wed, Jul 22, 2009 at 5:47 AM, Andreas > Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> Hi Daniel! >> >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached

I'm trying to validate some changes to send to trunk and I'm getting a bunch of test failures like this: Error opening '/ptmp/dag/build/llvm/staging/debug/Debug+Asserts/lib/libprofile_rt.so': /ptmp/dag/build/llvm/staging/debug/Debug+Asserts/lib/libprofile_rt.so: cannot open shared object file: No such file or directory Indeed there is no libprofile_rt.so. When I build from

Hi Rantao, perhaps you should use $llvmpath/utils/profile.pl for profiling? It works well. If you don't want to use it, there is at least some code in the script that should help you. BTW: I'm not sure if it is possible to instrument the bitcode with function and basic block code at the same time. But it should work sequential (data in llvmprof.out are accumulated after each run

Hi, sorry but I can't found where the profiling data (llvmprof.out[?]) is generated. Perhaps soembody has a hint for me? Thank you very much Nico