similar to: [LLVMdev] Querying Path Profile Data

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

David Greene wrote: > 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. >> >>

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

This proposal adds support for path profiling [Ball96] to LLVM. Path profiling compactly represents acyclic paths in a directed acyclic graph representation of the control flow graph of a routine. Instrumentation can be added to uniquely identify paths executed at runtime. Path profiles enable precise enumeration of the sequence of basic blocks executed in order for a particular path. Using path

Hi all, I plan to improve the existing profiling support in LLVM for my master thesis. The goal is threefold: a) Implement more efficient instrumentation along the lines of [Ball94]. b) Implement and experiment with heuristic estimators as proposed in [Wu94]. c) Make profile information available in the backend machinery. We have a preliminary patch that achieves this by maintaining

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

Ball Larus path profiling requires temporarily changing the CFG by replacing backedges (such as those caused by loops) in order to determine instrumentation placement, and attaching increments to edges [Ball96]. As far as I understand the CFG available through the BasicBlock class directly corresponds to the IR. I would rather not change the IR except to insert the profiling code. So, is

Hi, this is the fourth in a series of patches to cleanup and improve the LLVM Profiling Infrastructure. It depends on the previous patches from http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-July/023569.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-July/023602.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-July/023642.html This patch introduces an implementation of the ProfileInfo

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

A student pointed out to me the article http://www.wired.com/news/politics/0,1283,51106,00.html describing recent testimony by Patrick Ball, the deputy director of the science and human rights program at the American Association for the Advancement of Science, at the war crimes trial of Slobodan Milosevic, the former Yugoslav president. Mr. Ball testified on a statistical analysis of the

Andreas Neustifter wrote: > Hi, > > I try to create a array that has a nonzero initialiser: > > What i do is, first create the array type. > > > const ArrayType *ATy = ArrayType::get(Type::Int32Ty, NumEdges); > > Then create some constant values for the initializer. > > > std::vector<Constant*> Initializer; Initializer.reserve(NumEdges); > >

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

Dear LLVM Developers: I am an undergraduate summer research student supervised by José Nelson Amaral at the University of Alberta. My work will primarily involve value profiling and path profiling. Andreas Neustifter is planning some changes to the profiling related code in LLVM (http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-February/020396.html). Are any of these changes in yet? Which

Is there currently a way to get static profiling information for a program (e.g. an implementation of "Static Branch Frequency and Program Profile Analysis" by Wu and Larus, or something more recent) using an LLVM pass? Sean -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello all, I would like to participate in this year's Google Summer of Code and I am sending you a short description of my proposal. I have written the formal proposal already and if someone is interested I can send him the pdf. One of the open projects in the LLVM list is to enhance LLVM with static profiling capabilities. LLVM already provides a unified structure for writing pro

Hi, I try to create a array that has a nonzero initialiser: What i do is, first create the array type. > const ArrayType *ATy = ArrayType::get(Type::Int32Ty, NumEdges); Then create some constant values for the initializer. > std::vector<Constant*> Initializer; Initializer.reserve(NumEdges); > APInt zero(32,0); Constant* zeroc = ConstantInt::get(zero); > APInt

On Wed, Aug 13, 2008 at 7:00 PM, Sean Soria <sean.soria at gmail.com> wrote: > Is there currently a way to get static profiling information for a program > (e.g. an implementation of "Static Branch Frequency and Program Profile > Analysis" by Wu and Larus, or something more recent) using an LLVM pass? the profiling code, which has bitrotted considerably, supports random

I want to get path profiling information with LLVM. LLVM provides methods for path profiling.I also get the llvmprof.out successfully. So I want to output the result.With llvm-prof ,I get the 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:

Hi Vedant, I would like to clarify that the proposal does *intra-procedural* path profiling as described in [Ball96]. > > This proposal adds support for path profiling [Ball96] to LLVM. Path profiling compactly represents acyclic paths in a directed acyclic graph representation of the control flow graph of a routine. Instrumentation can be added to uniquely identify paths executed at

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