search for: blockprofil

...to qualify it for the release. -Tanya > make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' > make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ > libprofile' > llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) > llvm[2]: Compiling BlockProfiling.c for Release build (PIC) > llvm[2]: Compiling CommonProfiling.c for Release build (PIC) > llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) > llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) > llvm[2]: Linking Release Loadable Module profile_rt.dll > /usr/l...

...nd clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]: Compiling CommonProfiling.c for Release build (PIC) llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) llvm[2]: Linking Release Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/3.4...

...aron > -Tanya > >> make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' >> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >> libprofile' >> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >> llvm[2]: Linking Release Loadable Module profile_rt...

...t; >>> make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' >>> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >>> libprofile' >>> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >>> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >>> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >>> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >>> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >>> llvm[2]: Linking Release Loadable M...

...make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' >>>> make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/ >>>> libprofile' >>>> llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) >>>> llvm[2]: Compiling BlockProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling CommonProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) >>>> llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) >>>> llvm[2]: Linking Re...

...' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering directory `/home/ang/build/llvm-coff/runtime' make[2]: Entering directory `/home/ang/build/llvm-coff/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]: Compiling CommonProfiling.c for Release build (PIC) llvm[2]: Compiling EdgeProfiling.c for Release build (PIC) llvm[2]: Compiling FunctionProfiling.c for Release build (PIC) PIC seems to be enabled for some strange reason, even with --disable-pic on configure....

> What I want to do is to insert a call funcation into each basic > block, which is for statistic some information. I recommend that you look at the various pieces of code under llvm/lib/Transforms/Instrumentation, e.g. BlockProfiling.cpp and TraceBasicBlocks.cpp. They do essentially the same thing as you are trying to do. > 1) I implement call function in another c/cpp file and > can I insert the external call function to existed > bytecode ? if it is valid. Can you give me a simple > example to show how to do i...

Hi llvmer, I am trying to learn how to use llvm. My question is described as the following, there has already a testcase code, and I get bytecode by using llvmgcc. What I want to do is to insert a call funcation into each basic block, which is for statistic some information. 1) I implement call function in another c/cpp file and can I insert the external call function to existed bytecode ? if it

...on. > Reply-To: llvmdev at cs.uiuc.edu > > > What I want to do is to insert a call funcation into each basic > > block, which is for statistic some information. > > I recommend that you look at the various pieces of code under > llvm/lib/Transforms/Instrumentation, e.g. BlockProfiling.cpp and > TraceBasicBlocks.cpp. They do essentially the same thing as you are > trying to do. > > > 1) I implement call function in another c/cpp file and > > can I insert the external call function to existed > > bytecode ? if it is valid. Can you give me a simple &g...

...(.text+0xca): undefined reference to `_malloc' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/BasicBlockTracing.o:BasicBlockTracing.c:(.text+0xe8): undefined reference to `_atexit' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/BlockProfiling.o:BlockProfiling.c:(.text+0x65): undefined reference to `_atexit' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/CommonProfiling.o:CommonProfiling.c:(.text+0x76): undefined reference to `_strdup' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/...

...lvm-van-install/bin/../lib -internalize-public-api-file=.../llvm-svn/runtime/libprofile/exported_symbols.lst -o .../llvm-svn-debug-obj/runtime/libprofile/Debug/profile_rt.internalize .../llvm-svn-debug-obj/runtime/libprofile/Debug/BasicBlockTracing.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/BlockProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/CommonProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/EdgeProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/FunctionProfiling.bc .../llvm-svn-debug-obj/runtime/libprofile/Debug/OptimalEdgeProfiling.bc make[1]: *** [.../ll...

Hi, I am trying to obtain basic block profiles for mediabench g721 benchmark. I have successfully built llvm in profile_enabling mode. Then so as to find out the block execution frequency, I ran the command, analyze encode.out-cbe. It generated gmon.out which I read using gprof. However, I did not get the basic block level execution frequency. Can anybody help me as to how I can extract the basic

...; <int> [#uses=1] store int %inc.1, int* %.numlocal_2 ret int %tmp.5 endif: ; preds = %entry ;;; Executed 102 times. ret int %tmp.5 } </snip> If you're interested, this is implemented by the following code: lib/Transforms/Instrumentation/BlockProfiling.cpp runtime/libprofile/ tools/llvm-prof/ utils/profile.pl I have given only a little thought on how to integrate this with the JIT and runtime system, but perhaps this is a step towards FDO. The code should be pretty simple to extend to new profiling implementations, and add lots of cool featu...

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

...t; > <File > RelativePath="..\..\lib\Transforms\TransformInternals.h"> > </File> > <Filter > Name="Instrumentation" > Filter=""> > <File > RelativePath="..\..\lib\Transforms\Instrumentation\BlockProfiling.cpp"> > </File> > <File > RelativePath="..\..\lib\Transforms\Instrumentation\EdgeProfiling.cpp"> > </File> > <File > RelativePath="..\..\lib\Transforms\Instrumentation\EmitFunctions.cpp"> > &lt...