search for: optimaledgeprofiling

..._sort' is not a member of 'std' which I find kind of curious since std::stable_sort didn't make a problem in the specific implementation. This problem aside I get the error $> llvm[2]: Linking Debug executable opt $> .../llvm-svn-debug-obj/Debug/lib/libLLVMInstrumentation.a(OptimalEdgeProfiling.o): In function `(anonymous namespace)::OptimalEdgeProfiler::runOnModule(llvm::Module&)': $> .../llvm/llvm-svn/lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp:135: undefined reference to `llvm::MaximumSpanningTree<llvm::BasicBlock const*>::MaximumSpanningTree(std::vector&lt...

...ything that definitely pulls <algorithm> in, so it may be a case of one implementation happening to do it, and the other not. > This problem aside I get the error > > $> llvm[2]: Linking Debug executable opt > $> > .../llvm-svn-debug-obj/Debug/lib/libLLVMInstrumentation.a(OptimalEdgeProfiling.o): > In function `(anonymous > namespace)::OptimalEdgeProfiler::runOnModule(llvm::Module&)': > $> > .../llvm/llvm-svn/lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp:135: > undefined reference to `llvm::MaximumSpanningTree<llvm::BasicBlock > const*>::Maxi...

...Info.cpp # deleted: lib/Analysis/ProfileInfoLoader.cpp # deleted: lib/Analysis/ProfileInfoLoaderPass.cpp # deleted: lib/Analysis/ProfileVerifierPass.cpp # deleted: lib/Transforms/Instrumentation/EdgeProfiling.cpp # deleted: lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp # deleted: lib/Transforms/Instrumentation/PathProfiling.cpp Please let me know if you have any concerns. I'm likely to submit this rather soon and revert it if I hear any problems because we've already spent too much time with newcomers looking at this code, trying to do stuff...

Hi guys, I am trying to perform edge profiling using on hello.bc file by using following command opt -insert-edge-profiling hello.bc -o hello-edge.bc but I get the error that option "-insert-edge-profiling" is unknown. Can you please help me to solve the issue. Please note that I am following the paper available at this link http://llvm.org/pubs/2010-12-Preuss-PathProfiling.pdf

...bug-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' make: *** [libprofile/.makeinstall] Error 2 Any toughts? (I attach the build log, so it does not get garbled.) Andi -- =============...

...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 + )

...eted: lib/Analysis/ProfileInfoLoader.cpp > # deleted: lib/Analysis/ProfileInfoLoaderPass.cpp > # deleted: lib/Analysis/ProfileVerifierPass.cpp > # deleted: lib/Transforms/Instrumentation/EdgeProfiling.cpp > # deleted: lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp > # deleted: lib/Transforms/Instrumentation/PathProfiling.cpp > > Please let me know if you have any concerns. I'm likely to submit this > rather soon and revert it if I hear any problems because we've already > spent too much time with newcomers looking at this...

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

...es/LLVMSupport.dir/APFloat.cpp.o] Error 1 > make[1]: *** [lib/Support/CMakeFiles/LLVMSupport.dir/all] Error 2 > [ 0%] Building C object > runtime/libprofile/CMakeFiles/profile_rt-shared.dir/EdgeProfiling.c.o > Building C object > runtime/libprofile/CMakeFiles/profile_rt-shared.dir/OptimalEdgeProfiling.c.o > > Linking C shared library ../../lib/profile_rt.so > [ 0%] Built target profile_rt-shared > make: *** [all] Error 2 > mdriftmeyer at horus:~/DeveloperProjects/LLVMProject/cmake-llvm$ Of course if I configure as follows:; > mdriftmeyer at horus:~/DeveloperProjects/LLVMPro...

...ation works in LLVM. Once the coding period begins I will first want to start working with the profiling infrastructure directly. I will modify the profiler so that run-time instrumentation is not inserted for loops with iterations counts that are known at compile time. This will be added to OptimalEdgeProfiling.cpp, and assuming it has a very-low compile-time overhead it will also be added to EdgeProfiling.cpp. Test-cases will be created for "test", and compile-time overhead and run-time benefits will be measured using "test-suite". After this three transforms will be modified to...

Hi folk, I'm a newbie to llvm, please first forgive my naive questions. I want to instrument llvm code to do some run-time monitoring work. After reading some of the llvm documentation, it begins clear to me that I can do the instrumentation in a transformation pass. There are several things I want to do in the transformation pass, but I'm not sure whether they are doable and how to do

Hi Andreas, First, thanks again for undertaking this work and submitting it back. There is a lot of good stuff here and it would be great to see it get back into the tree. I have a few major high-level comments on the patch. First off, the patch is quite large and should be broken down into separate incremental changes which are easier to review and apply. I think the patches should more or less

Hi all, as proposed in http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-February/020396.html I implemented the algorithm presented in [Ball94]. It only instruments the minimal number of edges necessary for edge profiling. The main changes introduced by this patch are: *) a interface compatible rewrite of ProfileInfo *) a cleanup of ProfileInfoLoader (some functionality in ProfileInfoLoader

Hi Daniel, Daniel Dunbar wrote: > Hi Andreas, > > First, thanks again for undertaking this work and submitting it back. There is a > lot of good stuff here and it would be great to see it get back into the tree. Thanks for taking the time to review this, I know its a huge patch. I still have a few questions on how you would like this patch to be re-factored and split up. > [...]