Displaying 3 results from an estimated 3 matches for "blocksrequired".
2009 Jul 10
3
[LLVMdev] Path profiling interface proposal
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
2009 Jul 10
0
[LLVMdev] Path profiling interface proposal
...these questions are answered later in your document but they really
need to be specified up front. PathProfileInfo::DESC, for example, has no
meaning outside of the comments in this context:
> /* Query for paths in hot to cold order. */
> PathProfileInfo::iterator path = PI.selectPaths(F, blocksRequired.begin(),
> blocksRequired.end(), PathProfileInfo::DESC);
All in all, looks good. This will be a useful addition.
-Dave
2009 Jul 11
1
[LLVMdev] Path profiling interface proposal
...swered later in your document but they really
> need to be specified up front. PathProfileInfo::DESC, for example, has no
> meaning outside of the comments in this context:
>
>> /* Query for paths in hot to cold order. */
>> PathProfileInfo::iterator path = PI.selectPaths(F, blocksRequired.begin(),
>> blocksRequired.end(), PathProfileInfo::DESC);
>
> All in all, looks good. This will be a useful addition.
Thanks for the feedback.
>
> -Dave
> _______________________________________________
> LLVM Developers mailing list
>...