Displaying 4 results from an estimated 4 matches for "functioncount".
Did you mean:
functioncounts
2012 May 22
1
[LLVMdev] unable to decode llvmpro.out for path profiling
...;llvmprof.out" manually and found that it dumps
different profile data for different input files.
For example for bzip2.c is dumps like this:
* Pty = 1*
* SavedArgslength=10*
* SavedArgs=(null)*
* *
* 4*<unsigned> random data , that i cant figure out*
* *
* Profile Header: 5*
* functionCount = 47*
* Function Id = 4 NumPathsExecuted = 36*
* path1 : count1*
* path2 : count2 and so on...*
*
*
But also this format is not same for all input file. For gzip.c and gcc.c
it stores data in some different manner.
I urgently need some suggestions and solutions about this problem.
Thanks in ad...
2009 Jul 01
0
[LLVMdev] Profiling in LLVM Patch
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
2009 Jun 29
7
[LLVMdev] Profiling in LLVM Patch
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
2009 Jul 01
12
[LLVMdev] Profiling in LLVM Patch
...h providing a ProfileInfo
> level API to query whether any information is present for a particular function
> so that clients don't perform needless queries.
I have to look into this one, I guess its possible to do this kind of check on demand and calculate BlockCounts from EdgeCounts and FunctionCounts form BlockCounts when necessary.
>> --- llvm-van/lib/Analysis/MaximumSpanningTree.cpp 1970-01-01 01:00:00.000000000 +0100
>> +++ llvm-c7/lib/Analysis/MaximumSpanningTree.cpp 2009-06-26 16:47:01.000000000 +0200
> ...
>> +#define WOOD_REP(M,V1,V2) \
>
> Please u...