similar to: [LLVMdev] Profiling Framework in Next Version of LLVM(3.2 maybe?)

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, I am using Path Profiling to path profile a C code. I'm using this commands: $ llvm-gcc -c -emit-llvm file.c -o file.bc $ opt --insert-hotpath-profiling file.bc -o file.ins.bc $ llc -march=x86 file.ins.bc -o file.ins.s $ gcc -I llvm2.9/runtime/PathProfling.c -I llvm2.9/runtime/CommonProfiling.c $ ./a.out This will give me path profile of of program in 'llvmpro.out' to decode

Hello Alastair, Yeah like I said, I was not aware of the new profile framework being developed. Interestingly BPI and BFI didnt turn up in any searches either. Anyway, I will take a look at them and see how they differ from the existing tools. Profile.pl is understandably a very simple script, but it does make it easier to see some preliminary profile results and identity the hot portions of a

Good Morning. On 22.07.09 14:47), Andreas Neustifter wrote: > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a regression in >> llvm-prof's behavior. I tried running edge profiling on the >>

Sorry, forgot attachment. On 23.07.09 07:40), Andreas Neustifter wrote: > Good Morning. > > On 22.07.09 14:47), Andreas Neustifter wrote: >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached >>> patch. There may be some missed merge errors. The main problem I have >>> with the rest of this patch is that it

Hi Alok, On 16/07/12 12:41, #ALOK PRAKASH# wrote: > I have been using the Profile.pl and the related passes and > optimizations for about 4 years now. With every new release lately, the > support for the profile scripts and their framework seemed to be > downgrading. Hence, I used my own tiny one line fixes to keep them > working. I offered to send these small patches to keep these

Hi members, I am a LLVM newbee. I am working in path profiling. I got an error message when reading the path profile data I made a sample source named foo.c The command chain to make llvm path profiling as follows: 1. Compile to LLVM Bitcode llvm-gcc –emit-llvm foo.c –c –o foo.bc 2. Insert Path Instruments opt –insert-path-profiling foo.bc –o foo_path.bc 3. Link with profile

Hi Andreas, Sorry for the lag time... On Wed, Jul 22, 2009 at 5:47 AM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: > Hi Daniel! > > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a

Hi Rantao, perhaps you should use $llvmpath/utils/profile.pl for profiling? It works well. If you don't want to use it, there is at least some code in the script that should help you. BTW: I'm not sure if it is possible to instrument the bitcode with function and basic block code at the same time. But it should work sequential (data in llvmprof.out are accumulated after each run

Hi! Daniel Dunbar wrote: > > Sorry for the lag time... No problem. As long as I know that you get to it sometime its fine for me... > On Wed, Jul 22, 2009 at 5:47 AM, Andreas > Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> Hi Daniel! >> >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached

On Wed, Aug 5, 2009 at 12:22 PM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> On Wed, Jul 22, 2009 at 5:47 AM, Andreas >> Neustifter<e0325716 at student.tuwien.ac.at> wrote: >>> >>> Hi Daniel! >>> >>> Daniel Dunbar wrote: >>>> >>>> I merged in my changes to your patch, which results in the

Hi Daniel! Daniel Dunbar wrote: > I merged in my changes to your patch, which results in the attached > patch. There may be some missed merge errors. The main problem I have > with the rest of this patch is that it causes a regression in > llvm-prof's behavior. I tried running edge profiling on the > MultiSource/Applications/aha benchmark in the llvm test-suite, and >

Hello, My name is Rantao Chen and i am a student at the University of Maryland. I am currently doing some research for a professor to do Basic Block profiling using LLVM. I have set up the environment correctly and built the profile_rt.so shared library, but i am having some problems using the LLVM profiling tools. I run "opt -insert-function-profiling -insert-block-profiling input.bc

Hi Alok, On 17/07/12 13:00, #ALOK PRAKASH# wrote: > Profile.pl is understandably a very simple script, but it does make > it easier to see some preliminary profile results and identity the > hot portions of a program which are suitable for hardware > acceleration. llvm-prof also helps in the same way. Ok, great -- using llvm-prof for detecting hot portions is the obvious use, but I

Hi All, I use llvm version 2.9. llvm-prof does not support to read path profiling info. So could I use any way else to read path profiling info? Thanks Linh ________________________________ From: Andreas Neustifter <andreas.neustifter at gmail.com> To: Andrew Trick <atrick at apple.com> Cc: Linh Ho Tran <hotranlinh at yahoo.com>; "llvmdev at cs.uiuc.edu Mailing

Hi All! I was involved in the LLVM profiling business during late 2009 and early 2010 but I was not working on the path profiling but the "regular" profiling code. So I'm only guessing in case there is not other answer. On 9 May 2011 20:19, Andrew Trick <atrick at apple.com> wrote: > > On May 9, 2011, at 3:36 AM, Linh Ho Tran wrote: > > [...] > > The error

Hi, sorry but I can't found where the profiling data (llvmprof.out[?]) is generated. Perhaps soembody has a hint for me? Thank you very much Nico

Hi, On Nov 1, 2006, at 7:31 PM, Chris Lattner wrote: > On Wed, 1 Nov 2006, Nico Moser wrote: >> sorry but I can't found where the profiling data (llvmprof.out[?]) is >> generated. Perhaps soembody has a hint for me? > > Take a look at how the llvm/utils/profile.pl script works. In this script the lli command get the load-argument "somewhere/ profile_rt.so".

On Wed, 1 Nov 2006, Nico Moser wrote: > sorry but I can't found where the profiling data (llvmprof.out[?]) is > generated. Perhaps soembody has a hint for me? Take a look at how the llvm/utils/profile.pl script works. -Chris -- http://nondot.org/sabre/ http://llvm.org/