similar to: [LLVMdev] Reviewer for our Path Profiling Implementation

On Dec 3, 2010, at 11:21 AM, Adam Preuss wrote: > 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

Thank you for your suggestions on the patch. If the patch is committed, I would be willing to maintain it, though I am not sure what is all involved or how I am made aware of changes that need to be made. The technical report https://www.cs.ualberta.ca/system/files/tech_report/2010/PreussPathProfLLVM.pdf contains my benchmarks relating to profiling overhead in LLVM. Over the next week I will

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

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

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

BTW, this will also remove the entire 'runtime' directory in the LLVM repository. Runtime libraries are now being developed in compiler-rt. That is where the GCDA profiling runtime already lives and any new instrumentation based profiling runtime would also likely live there. If the code in the existing runtime tree is needed to start building those, they can always be found in the VCS

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

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

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

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

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

Dear all, I have already checked some related posted messages, such as: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/012315.html and http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-February/012466.html After getting rid of some error messages, I was able to run the following commands: 1) opt -insert-path-profiling matmul.bc -o matmul.pp.bc 2) lli -load

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

On Friday 10 July 2009 18:06, Slobodan Pejic wrote: > 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, This

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Hello Everyone, Before I get started I just want to sincerely apologise for not getting feedback on this earlier. I've had an extremely busy week as I was presenting a paper at the CGO conference. If anyone is able to provide feedback in such a short time-frame then it will be gratefully received. If not, then I just hope the work described sounds useful. I have already submitted

Adam, Path profiling would be a useful addition to LLVM but that by itself is not enough to include it in mainline LLVM. There has to be someone willing to maintain it as well, including bug fixes and code updates as LLVM APIs change. Is that something you are willing to do? --Vikram Associate Professor, Computer Science University of Illinois at Urbana-Champaign http://llvm.org/~vadve

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 printed in pathprofile module but in

Dear R developers, concerning the stats package, is there a way to access more of the 'internal' parameters of the optim() methods (e.g. BFGS), without me rewriting optim code and using it as an internal, patched stats package? It may not sound useful to you, but for me it is important to be able to change the parameters as I want to apply parameter tuning methods. Currently, I'm

Summary: We need to find a reviewer for our implementation of Ball-Laurus path profiling. It is well known that path profiling generates more precise information about a program's behaviour than edge profiling. We are conducting a research project with the goal of developing a methodology to make feedback-directed optimization (FDO) more sound. We are developing combined profiles that enable