similar to: [LLVMdev] Determine branch coverage information

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

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

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

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

Hi gang, time for my weekly confusion... (I'm trying not to bombard the board with questions) The thing that's on my mind at the moment (there's some backend-stuff that I'm just working my way though) is that I'm not getting very far when trying to get LLVM to profile code - I'm looking for nothing more special than list of how many times each basic block has been called

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

On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > Hi All, > > I think Nick's suggestion is correct, my code was linked against > libprofile_rt.a, which had gcda profiling code before, but was removed > https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff > > So, I couldn't find the correct symbols from

Thanks for your reply. May I know which is the recommended library that should be linked against? I am currently linking libprofile_rt.a. And I have noticed the differences that, if we do `nm libprofile_rt.a | grep llvm` with my old copy of the llvm/clang installation, I can see 00000000000005e0 T _llvm_gcda_emit_arcs 0000000000000b48 S _llvm_gcda_emit_arcs.eh 0000000000000430 T

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 >

Hello list, I've been having a tough time adding windows resource support to my ogg vorbise decoder, although I think I am close. Basically when I call ov_open_callbacks(), it doesn't ever return and repeatedly calls my seek_func. I'm hoping it is something obvious, but I can't see why my seek_func is being called endlessly. If the file is seekable, I should return 0, right? If

Hi! On Fri, Mar 15, 2013 at 10:51 PM, Qun Fa <testforqunfa at gmail.com> wrote: > Thank you Alexey. > > I have tried to use Makefile. This will generate the correct symbols that > I need. > > Any idea on the schedule of adding CMake support to compiler-rt? > Starting from r177382 CMake on Linux should build the same profile compiler-rt library as Makefiles. >

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

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 All, I think Nick's suggestion is correct, my code was linked against libprofile_rt.a, which had gcda profiling code before, but was removed https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff So, I couldn't find the correct symbols from libprofile_rt.a any more. Now my assumption is I need to use the correct library that is provided by compiler-rt.

Thank you Alexey. I have tried to use Makefile. This will generate the correct symbols that I need. Any idea on the schedule of adding CMake support to compiler-rt? Sincerely, Qun On Fri, Mar 15, 2013 at 1:51 AM, Alexey Samsonov <samsonov at google.com>wrote: > > On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > >> Hi All, >>

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

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

Thank you Alexey. I will try this out this week. Any idea on supporting this for Mac? My raw idea is to add this to compiler-rt/lib/profile/CMakeLists.txt if(APPLE) foreach(arch ${PROFILE_SUPPORTED_ARCH}) add_compiler_rt_static_runtime(clang_rt.profile-${arch} ${arch} SOURCES ${PROFILE_SOURCES} CFLAGS --sysroot=${COMPILER_RT_DARWIN_SDK_SYSROOT}) endforeach() endif() Do you

Hi, How can I use profile information into my pass for performing some analysis. I tried something like: PassManager PassMgr = PassManager(); cl::opt<std::string> ProfileDataFile(cl::Positional, cl::desc("<llvmprof.out file>"), cl::Optional, cl::init("llvmprof.out")); PassMgr.add(createProfileLoaderPass(ProfileDataFile));

On Mon, Mar 25, 2013 at 5:04 PM, Qun Fa <testforqunfa at gmail.com> wrote: > Thank you Alexey. I will try this out this week. Any idea on supporting > this for Mac? > > My raw idea is to add this to compiler-rt/lib/profile/CMakeLists.txt > > if(APPLE) > foreach(arch ${PROFILE_SUPPORTED_ARCH}) > add_compiler_rt_static_runtime(clang_rt.profile-${arch} ${arch}