search for: lprofile_rt

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: ===-------------------------------------------------------------------------=== Function execution frequencies: ## Frequency 1. 4.3e+05/708539 main 2. 2....

...nswers 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 profiling information using You can also skip the compilation step and run directly through the interpreter lli -load /llvms/lib/libprofile_rt.so sort_prof.bc > llvm-prof sort_prof.bc, and the result is: > try run...

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

...e 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 runtime library and make machine code llvm-ld –lprofile_rt –native foo_path.bc –o foo_path 4. Run program to get profile info ./foo_path –llvmprof-out 5. Create path count map from raw data opt –path-profile-loader-file =llvmprof.out –path-profile-loader foo_path.bc –o path.out 6. Load Profile info: llvm-prof path.out The error message fr...

...lLLVMInterpreter -lLLVMipa -lLLVMipo -lLLVMJIT -lLLVMLinker -lLLVMMC - lLLVMScalarOpts -lLLVMSelectionDAG -lLLVMSupport -lLLVMSystem - lLLVMTarget -lLLVMTransformUtils -lLLVMX86AsmParser - lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMX86Info -lLTO -lLTO - lplugin_llvmc_Base -lplugin_llvmc_Clang -lprofile_rt -framework MaxAudioAPI -framework MaxAPI -framework Carbon -o "/sysbuild/ Development/codegen.mxo/Contents/MacOS/codegen" Undefined symbols: "_backtrace", referenced from: PrintStackTrace(void*) in libLLVMSystem.a(Signals.o) ld: symbol(s) not found collect2: ld retu...

...lLLVMipa -lLLVMipo -lLLVMJIT -lLLVMLinker - > lLLVMMC -lLLVMScalarOpts -lLLVMSelectionDAG -lLLVMSupport - > lLLVMSystem -lLLVMTarget -lLLVMTransformUtils -lLLVMX86AsmParser - > lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMX86Info -lLTO -lLTO - > lplugin_llvmc_Base -lplugin_llvmc_Clang -lprofile_rt -framework > MaxAudioAPI -framework MaxAPI -framework Carbon -o "/sysbuild/ > Development/codegen.mxo/Contents/MacOS/codegen" > Undefined symbols: > "_backtrace", referenced from: > PrintStackTrace(void*) in libLLVMSystem.a(Signals.o) > ld: symbol(s)...

Eli Gottlieb <eligottlieb at gmail.com> writes: > I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To > do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and > did a slight rewrite of my CMakeLists.txt file for building the C > code. > > Problem is, cmake no longer finishes at all. I receive the > following output, and then

...r delete's and main's paths and zero values for print's and insert's paths. This problem occurs only with -O3 option. It is working correctly with llvm-gcc -O1 I first generated .ll fine using llvm-gcc -O3 and then used opt to insert path profiling. Then used llvm-as and llvm-ld -lprofile_rt to get the executable. Can you suggest what went wrong? Thanking you Unnikrishnan C Research Scholar Indian Institute of Science -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Hello. I've used these commands to compile the code below with edge-profiling-instrumentation: $> clang -emit-llvm -c rnd.c -o rnd.bc $> opt -insert-edge-profiling rnd.bc -o rnd-prof.bc $> clang rnd-prof.bc -lprofile_rt -L/paths/lib -o rnd this is the source: #include <stdio.h> void hello() { printf("hello\n"); } int main() { int i=0; for (i=0; i<149; i++) hello(); return 0; } and use these commands to see the profile information: $> llvm-prof rnd.bc and this is the output: .........

...I can find on these are from previous questions people have asked( https://groups.google.com/forum/#!topic/llvm-dev/vJ2wDsQY6a4 being one of them). The steps from what I can understand are: opt -insert-edge-profiling -O3 foo.bc -o foo.2.bc run the compiled binary using llvm-prof after linking with lprofile_rt opt -profile-loader -O3 foo.bc -o foo.opt.bc //the required info can be obtained using this pass. Because I cross compile the binary, I am using gem5 to run it. This means, I have a problem since I have an arm binary I need to execute and x86 llvm tool(llvm-prof in this case).Theoretically,...

...while(NOT "${expanded_components}" MATCHES "^${processed}(;)|(.*)") list(REMOVE_AT processed -1) endwhile() list(LENGTH processed cursor) However, using "all" as the component to be linked is still broken, as it passes to the linker -lLTO_static and -lprofile_rt-static, which are non-existant libraries on a static build. On the case of LTO_static the fix probably is diff --git a/tools/lto/CMakeLists.txt b/tools/lto/CMakeLists.txt index 9112976..60fc902 100644 --- a/tools/lto/CMakeLists.txt +++ b/tools/lto/CMakeLists.txt @@ -23,5 +23,4 @@ endif() if( N...

Hi again, I'm trying to upgrade my LLVM bindings in Java from 2.9 to 3.1. To do so, I regenerated the JNI bindings from fresh LLVM 3.1 headers, and did a slight rewrite of my CMakeLists.txt file for building the C code. Problem is, cmake no longer finishes at all. I receive the following output, and then it just runs forever (while still responding to a CTRL-C): > eli at

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > >> >> On Jan 14, 2009, at 12:44 PM,

Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > > On Jan 14, 2009, at 12:44 PM, Graham Wakefield wrote: > >> Sorry if this is a newb q... I'm developing an application on a >> 10.5 machine but want to target the 10.4 SDK. Is there a magic >> incantation for the llvm configure script to set the sysroot path, >> equivalent to e.g. --with-sysroot