search for: pathprofileinfo

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

...he intent for libprofile_rt to be the home for all profiling runtime or just path profiling? If the latter, I'd suggest a different name, like libpathprofile_rt. I'm not knowledgeable about the LLVM profiling infrastructure, so maybe libprofile_rt is something that already exists. > PathProfileInfo& profileInfo = getAnalysis <PathProfileInfo>(); PathProfileInfo is an ImmutablePass, yes? > /* > * The following method allows querying for path numbers by specifying > * F, the function that the paths are in; > * start, starting iterator over basic blocks; >...

...#39;d suggest a different name, like > libpathprofile_rt. I'm not knowledgeable about the LLVM profiling > infrastructure, so maybe libprofile_rt is something that already exists. Yes, libprofile_rt already exists, however it must be built by invoking make in runtime/. > >> PathProfileInfo& profileInfo = getAnalysis <PathProfileInfo>(); > > PathProfileInfo is an ImmutablePass, yes? > >> /* >> * The following method allows querying for path numbers by specifying >> * F, the function that the paths are in; >> * start, starting ite...

...error:llvm-prof: Unkknown packet #5. So I have to write my own pass to output the path profiling result,the following is my kernel codes: //////////////////////////////////////////////////////////////////////////////////// bool PathProfileOutput::runOnModule(Module &M) { PathProfileInfo& pathProfileInfo = getAnalysis<PathProfileInfo>(); for(Module::iterator F = M.begin();F != M.end(); ++F){ if (F->isDeclaration()) continue; pathProfileInfo.setCurrentFunction(F); for(ProfilePathIterator nextPath=pathProfileInfo.pathBegin();nextPath != pathP...

...confusing those efforts and so I would like to garbage collect and help pave the way for new stuff. We can always recover this code from the VCS if needed in the future. Files on the chopping block: # deleted: include/llvm/Analysis/PathNumbering.h # deleted: include/llvm/Analysis/PathProfileInfo.h # deleted: include/llvm/Analysis/ProfileDataLoader.h # deleted: include/llvm/Analysis/ProfileDataTypes.h # deleted: include/llvm/Analysis/ProfileInfo.h # deleted: include/llvm/Analysis/ProfileInfoLoader.h # deleted: include/llvm/Analysis/ProfileInfoTyp...

...overflow (i.e. supports path profiling across recursion) + Optimizations for use cases with very large number of executed paths + Used to analyse C/C++ benchmarks from SPECCPU2006 Proposed Integration : + Support library code added to compiler-rt + llvm/Analysis gets PathEncoding, PathDecoding and PathProfileInfo module passes + llvm/Transforms/Instrumentation gets PathProfileInstrumentation module pass + PathProfileInfo offers const only public methods to query info Open Issues : + Update PathProfileInfo on CFG transformations ? + Verify with PGOEdge info ? + Handle setjmp, longjmp, early program terminat...

...o I would > like to garbage collect and help pave the way for new stuff. We can always > recover this code from the VCS if needed in the future. > > Files on the chopping block: > # deleted: include/llvm/Analysis/PathNumbering.h > # deleted: include/llvm/Analysis/PathProfileInfo.h > # deleted: include/llvm/Analysis/ProfileDataLoader.h > # deleted: include/llvm/Analysis/ProfileDataTypes.h > # deleted: include/llvm/Analysis/ProfileInfo.h > # deleted: include/llvm/Analysis/ProfileInfoLoader.h > # deleted: include/llv...

...open shared object file: No such file or directory Indeed there is no libprofile_rt.so. When I build from trunk, I don't see these errors and I don't see anything in the build that talks about profiling at all. In contrast, in the tree with changes I see things like: llvm[2]: Compiling PathProfileInfo.cpp for Debug+Asserts build I did muck around a bit with configure.ac so I suppose I might have tripped something and enabled some kind of additional profile library build. Has anyone seen this before, or can someone help me understand what is going on? Thanks! -Davi...

...| >> 18m36.447s | 6m50.288s | 925863 | 925271 | >> >> +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ >> >> >> >> > > Open Issues : >> > > + Update PathProfileInfo on CFG transformations ? >> >> > Could you clarify what this means? >> >> Changing the control flow graph of a routine may invalidate collected path >> profiles. For example, splitting a block with an unconditional branch does >> not change the profile, but in...

...uot;path-profile-verifier-file", + cl::init("edgefrompath.llvmprof.out"), + cl::value_desc("filename"), + cl::desc("Edge profile file generated by -path-profile-verifier")); ... +// command line option for loading path profiles +static cl::opt<std::string> +PathProfileInfoFilename("path-profile-loader-file", cl::init("llvmprof.out"), + cl::value_desc("filename"), + cl::desc("Path profile file loaded by -path-profile-loader")); ... +// Are we enabling early termination +static cl::op...

...s | 6m50.288s | 925863 | 925271 | >>> >>> +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ >>> >>> >>> >>> > > Open Issues : >>> > > + Update PathProfileInfo on CFG transformations ? >>> >>> > Could you clarify what this means? >>> >>> Changing the control flow graph of a routine may invalidate collected path >>> profiles. For example, splitting a block with an unconditional branch does >>> not ch...

...;, > + cl::init("edgefrompath.llvmprof.out"), > + cl::value_desc("filename"), > + cl::desc("Edge profile file generated by -path-profile-verifier")); > ... > +// command line option for loading path profiles > +static cl::opt<std::string> > +PathProfileInfoFilename("path-profile-loader-file", cl::init("llvmprof.out"), > + cl::value_desc("filename"), > + cl::desc("Path profile file loaded by -path-profile-loader")); > ... > +// Are we enabling early termin...

...----------+ | namd | 59598954 | 0m4.124s | 0m4.139s | 43 | 18m36.447s | 6m50.288s | 925863 | 925271 | +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ > > Open Issues : > > + Update PathProfileInfo on CFG transformations ? > Could you clarify what this means? Changing the control flow graph of a routine may invalidate collected path profiles. For example, splitting a block with an unconditional branch does not change the profile, but introducing a conditional branch invalidates the profi...

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

...| > >>> > >>> > +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ > >>> > >>> > >>> > >>> > > Open Issues : > >>> > > + Update PathProfileInfo on CFG transformations ? > >>> > >>> > Could you clarify what this means? > >>> > >>> Changing the control flow graph of a routine may invalidate collected > path > >>> profiles. For example, splitting a block with an unconditional b...

...profiling at all. I just updated and did a clean recompile and I do have a libprofile_rt.so ($BUILD/Debug+Asserts/lib/libprofile_rt.so). Perhaps the configure changes have stopped it from being compiled. > In contrast, in the tree with changes I see things like: > > llvm[2]: Compiling PathProfileInfo.cpp for Debug+Asserts build That file is also compiled for me on trunk. It does not actually relate to libprofile_rt.so (in the current context). This is probably obvious, but: libprofile_rt.so is the runtime library that provides the functions that the profiling instrumentation code inserts...

...gt; >> >>> +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ >> >>> >> >>> >> >>> >> >>> > > Open Issues : >> >>> > > + Update PathProfileInfo on CFG transformations ? >> >>> >> >>> > Could you clarify what this means? >> >>> >> >>> Changing the control flow graph of a routine may invalidate collected >> >>> path >> >>> profiles. For example, spli...

...y, good branch-prediction behaviour and good scheduling for the "trace". Path-profiling may need to be fixed or enhanced for this, as it is currently unused it is difficult to know how well it will work. (Note: I'm stating that it is unused based on the fact that nothing includes PathProfileInfo.h except the path profiling itself — it is, however, possible that tools outside the core llvm use it though I couldn't find anything by means of an internet search). This will be tested and evaluated in the same way as the previously modified transformations. In all the above cases the mo...

hacker cling wrote: > Hello all, > I was playing with LLVM pass. I changed the > lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make > install the pass and use an example test1.c to see whether it works or > not. When I run example using the following command: > clang -emit-llvm test1.c -c -o test1.bc > opt -load

Hello all, I was playing with LLVM pass. I changed the lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make install the pass and use an example test1.c to see whether it works or not. When I run example using the following command: clang -emit-llvm test1.c -c -o test1.bc opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc > /dev/null It