search for: larus

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: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080813/55f46d60/attachment.html>

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 sampling based profiling of any of the llvm profiling passes. Andrew

...in the community, I would like to contribute the patches back to the official repository. If you have any comments, experiences, or advice on that matter, I would be happy to hear them upfront. Best Regards, Andreas Neustifter Vienna University of Technology [Ball94] Thomas Ball, James R. Larus: "Optimally profiling and tracing programs" ACM TOPLAS, Volume 16, Issue 4, 1994 http://portal.acm.org/citation.cfm?id=183527 [Wu94] Youfeng Wu, James R. Larus: Procedings of the 27th ACM International Symposium on Microarchitecture, 1994 http://portal.acm.org/citation.cfm?id=192724.19...

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

...mail/llvmdev/2009-July/023642.html This patch introduces an implementation of the ProfileInfo that estimates a profile as proposed in [Ball94]. (It distributes incoming flow in an block equally to the successor edges and assumes an loop iteration count of 10.) Andi [Ball94] Thomas Ball, James R. Larus: "Optimally profiling and tracing programs" ACM TOPLAS, Volume 16, Issue 4, 1994 http://portal.acm.org/citation.cfm?id=183527

...sa/tools/stprof-llvm.patch The implementation is based on Wu's [1994] paper and provides a branch predictor that calculates probabilities. The implementation also covers an intraprocedural and interprocedural frequency calculator for edges and functions. Reference: Youfeng Wu and James R. Larus. Static branch frequency and program profile analysis. In MICRO 27: Proceedings of the 27th annual international symposium on Microarchitecture. IEEE, 1994. Regards, Andrei On Tue, Nov 2, 2010 at 10:46 AM, Andrew Lenharth <andrewl at lenharth.org> wrote: > On Tue, Nov 2, 2010 at 12...

...based on Wu's [1994] paper and provides a >> branch predictor that calculates probabilities. The implementation >> also covers an intraprocedural and interprocedural frequency >> calculator for edges and functions. >> >> Reference: >> Youfeng Wu and James R. Larus. Static branch frequency and program >> profile analysis. In MICRO 27: Proceedings of the 27th annual >> international symposium on Microarchitecture. IEEE, 1994. >> >> Regards, >> Andrei >> >> On Tue, Nov 2, 2010 at 10:46 AM, Andrew Lenharth <andre...

...The implementation is based on Wu's [1994] paper and provides a > branch predictor that calculates probabilities. The implementation > also covers an intraprocedural and interprocedural frequency > calculator for edges and functions. > > Reference: > Youfeng Wu and James R. Larus. Static branch frequency and program > profile analysis. In MICRO 27: Proceedings of the 27th annual > international symposium on Microarchitecture. IEEE, 1994. > > Regards, > Andrei > > On Tue, Nov 2, 2010 at 10:46 AM, Andrew Lenharth <andrewl at lenharth.org> >...

...;>> branch predictor that calculates probabilities. The implementation > >>> also covers an intraprocedural and interprocedural frequency > >>> calculator for edges and functions. > >>> > >>> Reference: > >>> Youfeng Wu and James R. Larus. Static branch frequency and program > >>> profile analysis. In MICRO 27: Proceedings of the 27th annual > >>> international symposium on Microarchitecture. IEEE, 1994. > >>> > >>> Regards, > >>> Andrei > >>> > >>&...

...paper and provides a >>> branch predictor that calculates probabilities. The implementation >>> also covers an intraprocedural and interprocedural frequency >>> calculator for edges and functions. >>> >>>  Reference: >>> Youfeng Wu and James R. Larus. Static branch frequency and program >>> profile analysis. In MICRO 27: Proceedings of the 27th annual >>> international symposium on Microarchitecture. IEEE, 1994. >>> >>>  Regards, >>>    Andrei >>> >>> On Tue, Nov 2, 2010 at 10:46 AM...

...LLVM. I have been programming in C and C++ for more than five years and I have strong compiler background, as this is my current field of research. This project will be useful to my master's research and I believe it will be also useful to the LLVM community. Reference: Youfeng Wu and James R. Larus. Static branch frequency and program profile analysis. In MICRO 27: Proceedings of the 27th annual international symposium on Microarchitecture. IEEE, 1994.

...dictor that calculates probabilities. The implementation >> >>> also covers an intraprocedural and interprocedural frequency >> >>> calculator for edges and functions. >> >>> >> >>>  Reference: >> >>> Youfeng Wu and James R. Larus. Static branch frequency and program >> >>> profile analysis. In MICRO 27: Proceedings of the 27th annual >> >>> international symposium on Microarchitecture. IEEE, 1994. >> >>> >> >>>  Regards, >> >>>    Andrei >> &gt...

Hi, I'm trying to get a feel for what the LLVM community wants to get out of path profiles. Ball Larus path profiles contain counters for path numbers, but this raw information is not too useful. Some potential queries follow: - Given a path number, and function give a basic block iterator over the path. - Given a function give path numbers ordered by counts. - Given a basic block give path num...

On Tue, Nov 2, 2010 at 12:28 AM, kapil anand <kapilanand2 at gmail.com> wrote: > Hi all, > > Does LLVM infrastructure contain implementation of any static profiling > algorithm apart from "Spill-Weight" calculation present in Live Intervals > class? The future work page does suggest implementation of some "static > profiling" algorithms to make an

Hi all, Does LLVM infrastructure contain implementation of any static profiling algorithm apart from "Spill-Weight" calculation present in Live Intervals class? The future work page does suggest implementation of some "static profiling" algorithms to make an educated guesses about the relative execution frequencies of various parts of the code. Thanks --Kapil --------------

...e decision to use LLVM instead of, say, working with x86 directly. On the other hand, if you are only interested in a teaching tool, why not use something like SPIM for example? If your usage model is different than SPIM then explaining it may clarify how LLVM would fit. http://pages.cs.wisc.edu/~larus/spim.html - Daniel > Thanks, > M. McDonnell > > > --- On *Sat, 10/11/08, Daniel Dunbar <daniel at zuster.org>* wrote: > > From: Daniel Dunbar <daniel at zuster.org> > Subject: Re: [LLVMdev] C++ to C? > To: michaeldmcdonnell at yahoo.com, "LLVM Develop...

Ok. If it's at llvm ir level, it's very simple since everything is in SSA form. What are you trying to achieve though? Evan On Aug 19, 2008, at 6:51 PM, Sean Soria wrote: > It's done at the MachineFunctionPass level as far as I can tell (http://llvm.org/doxygen/classllvm_1_1LiveIntervals.html > ). I'd like something at the FunctionPass level. > > On Tue, Aug 19,

It's done at the MachineFunctionPass level as far as I can tell ( http://llvm.org/doxygen/classllvm_1_1LiveIntervals.html). I'd like something at the FunctionPass level. On Tue, Aug 19, 2008 at 6:11 PM, Evan Cheng <evan.cheng at apple.com> wrote: > I am not sure what you mean. Live interval analysis is done at the > function level. > > Evan > > On Aug 19, 2008,

...it up a little. I did not use the mkpatch utility since it does not include added files, I hope the format is readable enough (it should be...) I ran "make check" and there are not additional errors introduced by the patch. Grettings, Andreas Neustifter [Ball94] Thomas Ball, James R. Larus: "Optimally profiling and tracing programs" ACM TOPLAS, Volume 16, Issue 4, 1994 http://portal.acm.org/citation.cfm?id=183527 -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-r74306.optimal_profiling.patch Type: text/x-patch Size: 85518 bytes Desc:...

...e decision to use LLVM instead of, say, working with x86 directly. On the other hand, if you are only interested in a teaching tool, why not use something like SPIM for example? If your usage model is different than SPIM then explaining it may clarify how LLVM would fit. http://pages.cs.wisc.edu/~larus/spim.html  - Daniel   Thanks, M. McDonnell --- On Sat, 10/11/08, Daniel Dunbar <daniel at zuster.org> wrote: From: Daniel Dunbar <daniel at zuster.org> Subject: Re: [LLVMdev] C++ to C? To: michaeldmcdonnell at yahoo.com, "LLVM Developers Mailing List" <llvmdev a...