search for: pathprofiling

...ASH 1 Why not an enum? +typedef struct { + unsigned fnNumber; /* function number for these counters */ + unsigned numEntries; /* number of entries stored */ +} PathHeader; + +typedef struct { + unsigned pathNumber; + unsigned pathCounter; +} PathTableEntry; Being global types, they need a PathProfiling-specific name or prefix (there are other kinds of paths). To be proper, should they also be under: #if defined(__cplusplus) extern "C" { endif You may even want to remove the emacs hint "-*- C++ -*-" from both this header and Profiling.h +++ runtime/libprofile/Profiling.h +#...

...unsigned fnNumber; /* function number for these counters */ > + unsigned numEntries; /* number of entries stored */ > +} PathHeader; > + > +typedef struct { > + unsigned pathNumber; > + unsigned pathCounter; > +} PathTableEntry; > > Being global types, they need a PathProfiling-specific name or prefix > (there are other kinds of paths). To be proper, should they also be under: > #if defined(__cplusplus) > extern "C" { > endif > > You may even want to remove the emacs hint "-*- C++ -*-" from both > this header and Profiling.h >...

I am a student at the University of Alberta under the supervision of José Nelson Amaral, and I have been working on implementing path profiling into LLVM. I have completed my project and would like to submit it. We are looking for a reviewer for the path profiling implementation. We have sent previous requests to the llvmdev list but have so far been unsuccessful. Please see the attached

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 this code being here....

Hello, I modified the PathProfiling.cpp and run opt -inesrt-path-profiling. it works correctly ,but after path-profile is complete in Verifier::visitTerminatorInst it prints "Terminator found in the middle of a basic block!" . error is I added two basic blocks after return basic block and return has br label %newprint when...

Hi, I am a student at IIT Kanpur. I am working on Path Profiling, i just came with a need to know about the number of static paths in a program(actually in a function) before it's actually get run. As i saw in PathProfiling.c file in llvm\runtime\libprofile they are just storing the path information at run time and dynamically adding entries for the new path. But i need to know the number of static paths (total paths in a function ) whether they are executed or not. Please help me know that, can LLVM provide me with n...

...ing 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 Thanks Naveed Ul Mustafa

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 portion and the met...

Hi, I am a student at IIT Kanpur. I am working on Path Profiling, i just came with a need to know about the number of static paths in a program(actually in a function) before it's actually get run. As i saw in PathProfiling.c file in llvm\runtime\libprofile they are just storing the path information at run time and dynamically adding entries for the new path. But i need to know the number of static paths (total paths in a function ) whether they are executed or not. Please help me know that, can LLVM provide me with n...

...s 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't benefit from th...

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

...> > 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 looks interesting. I have a few questions. Is there anything about your proposed profiling method that requires the use of lli or llvm-ld? I'm assuming the instrumentor itself will simply be a Pass. Will this work in setups that use the machine's native linker as...

...n=-O3. Generated clang would be stable. But stage2-bin and stage3-bin will not match. Investigating. [PR6270] Without r127723, generated clang would be unavailable for parallel build. [PR9505] With -Asserts, I saw more two warnings, lib/Analysis/LazyValueInfo.cpp and lib/Transforms/Instrumentation/PathProfiling.cpp. * RC1 with patches. I have committed many patches for MSYS and mingw. With them, clang and llvm can pass tests without any failures. (On TOT, we can run mingw tests without failures!) [LLVM] - r127239, r127240 Availability of Lit on MSYS configure. - r127723 [PR6270] PathV1::makeUnique(...

...me/libprofile/CMakeLists.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 + )

...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, certainly the instr...

Dear Members, I am working on path profiling, but command llvm-prof cannot read path profile info. Making llvm-prof to be able to read PP info is so wonderful. But I cannot find the format of PP. Could anyone give me the document of path profile info format so that I could modify llvm-prof. Thank you in advance Linh Ho -------------- next part -------------- An HTML attachment was

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

...> fatal error: > 'cmath' file not found > #include <cmath>* > ^ > [ 0%] Building C object > runtime/libprofile/CMakeFiles/profile_rt-shared.dir/GCDAProfiling.c.o > [ 0%] Building C object > runtime/libprofile/CMakeFiles/profile_rt-shared.dir/PathProfiling.c.o > 1 error generated. > make[2]: *** > [lib/Transforms/Hello/CMakeFiles/LLVMHello.dir/Hello.cpp.o] Error 1 > make[1]: *** [lib/Transforms/Hello/CMakeFiles/LLVMHello.dir/all] Error 2 > make[1]: *** Waiting for unfinished jobs.... > 1 error generated. > [ 0%] make[2]: *** &...

...ning 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 looks interesting. I have a few questions. Thanks for taking the time to look through! > > Is there anything about your proposed profiling method that requires the > use of lli or llvm-ld? I'm assuming the instrumentor itself will simply...

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