search for: edgeprofiling

...ntering 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.4/../../../../i686-pc-cygwin/bin/ld: > warning: cannot find entry symbol __cygwin_dll_entry at 12; defau...

...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.4/../../../../i686-pc-cygwin/bin/ld: warning: cannot find entry symbol __cygwin_dll_entry at 12; defaulting to 61ec1000 /h...

I'm an LLVM newbie, trying to write a pass that adds instrumentation to a program, and have a couple of questions. For purposes of this discussion, suppose I'm trying to add a per-function counter that is incremented each time a function is called. At the end of the target program's execution, I would like to output the value of each counter. My questions are as follows: 1.

Alright, I'm ready to nuke it. Last chance to say stop. For context of others, this has come up repeatedly: no one we know of is using EdgeProfiling.cpp, PathProfiling.cpp, and the lib/Analysis/Profile*Pass.cpp collection of tools. They haven't been updated since 2012 when Alastair Murray looked into this stuff, and both current efforts towards PGO are essentially *totally* different implementation strategies that won't benefit from thi...

.../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.4/../../../../i686-pc-cygwin/bin/ld: >> warning: cannot find entry symbol __cygwin_dll_en...

...ir-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.4/../../../../i686-pc-cygwin/bin/ld: >>> warning: cannot find entry symbol...

Chandler Carruth wrote: >Alright, I'm ready to nuke it. Last chance to say stop. Stop. >For context of others, this has come up repeatedly: no one we know of is >using EdgeProfiling.cpp, PathProfiling.cpp, and the >lib/Analysis/Profile*Pass.cpp collection of tools. We've been actively using it since at least 2.8. True, we haven't been vocal about it. While I can see perhaps getting rid of some of the older ProfileInfoT related stuff, certainly the instrumentation...

...>>> 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.4/../../../../i686-pc-cygwin/bin/ld: >>>> warning: cannot f...

...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. Then there seems to be a missing library too :- llvm[2]: Linking Release Loadable Module profile_rt.dll /usr/lib/gcc/i68...

...nning to submit this tomorrow morning. -Chandler On Thu, Sep 12, 2013 at 8:22 PM, Chandler Carruth <chandlerc at google.com>wrote: > Alright, I'm ready to nuke it. Last chance to say stop. > > For context of others, this has come up repeatedly: no one we know of is > using EdgeProfiling.cpp, PathProfiling.cpp, and the > lib/Analysis/Profile*Pass.cpp collection of tools. They haven't been > updated since 2012 when Alastair Murray looked into this stuff, and both > current efforts towards PGO are essentially *totally* different > implementation strategies that won...

...how I could print the results of any analysis and transformation pass. Say, I have a program written in c and I ran the edge-profiling pass onto it. Now I want to see the result. How could I do it? Also if I happen to change one of the passes inside folder /llvm/lib/Transforms/Instrumentation (say EdgeProfiling.cpp), then what all do I have to do to see the changes done in the pass. Please help me with the required steps. And is there any tool available which I use to see the control flow(step by step execution of the code) when I execute say the -insert-edge-profiling pass on my bitecode. If there is on...

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

...information on the tools. Actually, I need to analyze which sections of code are prone to misses and mis predicts, and would have to eventually instrument the code. I was able to instrument and call an external function, but faced an issue while passing an argument to the function. I am following EdgeProfiling.cpp but couldn't figure out the problem. Could you please see where I am going wrong here - virtual bool runOnModule(Module &M) { Constant *hookFunc; LLVMContext& context = M.getContext(); hookFunc = M.getOrInsertFunction("cacheCou...

...:(.text+0x332): undefined reference to `_fprintf' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/CommonProfiling.o:CommonProfiling.c:(.text+0x33e): undefined reference to `_perror' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/EdgeProfiling.o:EdgeProfiling.c:(.text+0x65): undefined reference to `_atexit' /cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/runtime/libprofile/Release/FunctionProfiling.o:FunctionProfiling.c:(.text+0x65): undefined reference to `_atexit' /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../libpthread.a(t-d0...

...j/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]: *** [.../llvm-svn-debug-obj/Debug/lib/libprofile_rt.bca] Segmentation fault make[1]: Leaving directory `.../llvm-svn-debug-obj/runtime/libprofile&...

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 llvm-memory-profi...

...Lists.txt --- llvm-2.9/runtime/libprofile/CMakeLists.txt 1970-01-01 08:00:00.000000000 +0800 +++ llvm-2.9.new/runtime/libprofile/CMakeLists.txt 2011-04-24 15:41:56.549409372 +0800 @@ -0,0 +1,8 @@ +add_llvm_loadable_module( profile_rt + BasicBlockTracing.c + CommonProfiling.c + PathProfiling.c + EdgeProfiling.c + OptimalEdgeProfiling.c + Profiling.h + )

On Sep 13, 2013, at 11:05 AM, msharp at codeaurora.org wrote: > Chandler Carruth wrote: > >> Alright, I'm ready to nuke it. Last chance to say stop. > > Stop. > >> For context of others, this has come up repeatedly: no one we know of is >> using EdgeProfiling.cpp, PathProfiling.cpp, and the >> lib/Analysis/Profile*Pass.cpp collection of tools. > We've been actively using it since at least 2.8. True, we haven't been > vocal about it. > > While I can see perhaps getting rid of some of the older ProfileInfoT > related stuff,...

...s. Actually, I need to > analyze which sections of code are prone to misses and mis predicts, and > would have to eventually instrument the code. > > I was able to instrument and call an external function, but faced an issue > while passing an argument to the function. I am following EdgeProfiling.cpp > but couldn't figure out the problem. Could you please see where I am going > wrong here - > > virtual bool runOnModule(Module &M) > { > Constant *hookFunc; > LLVMContext& context = M.getContext(); > hookFunc...

Hi Nick Thanks for you reply. CMAKE is very new to me. I complied using GNU WIN32 and got those errors. Is it possible to compile it using GNU WIN 32 and anything need to be modified? I managed to compile the run time library on a mac machine. Yafan On Fri, Apr 22, 2011 at 5:04 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > yafan zhao wrote: > >> Hi All >> Thanks for