Displaying 5 results from an estimated 5 matches for "pathnumber".
Did you mean:
path_number
2010 Dec 08
0
[LLVMdev] Reviewer for our Path Profiling Implementation
...lp text.
+++ include/llvm/Analysis/ProfileInfoTypes.h
+#define PP_ARRAY 0
+#define PP_HASH 1
Why not an enum?
+typedef struct {
+ unsigned fnNumber; /* function number for these counters */
+ unsigned numEntries; /* number of entries stored */
+} PathHeader;
+
+typedef struct {
+ unsigned pathNumber;
+ unsigned pathCounter;
+} PathTableEntry;
Being global types, they need a PathProfiling-specific name or prefix
(there are other kinds of paths). To be proper, should they also be under:
#if defined(__cplusplus)
extern "C" {
endif
You may even want to remove the emacs hint "-*-...
2010 Dec 08
1
[LLVMdev] Reviewer for our Path Profiling Implementation
...+#define PP_ARRAY 0
> +#define PP_HASH 1
>
> Why not an enum?
>
> +typedef struct {
> + unsigned fnNumber; /* function number for these counters */
> + unsigned numEntries; /* number of entries stored */
> +} PathHeader;
> +
> +typedef struct {
> + unsigned pathNumber;
> + unsigned pathCounter;
> +} PathTableEntry;
>
> Being global types, they need a PathProfiling-specific name or prefix
> (there are other kinds of paths). To be proper, should they also be under:
> #if defined(__cplusplus)
> extern "C" {
> endif
>
> You...
2010 Dec 03
4
[LLVMdev] Reviewer for our Path Profiling Implementation
I am a student at the University of Alberta under the
supervision of José Nelson Amaral, and I have been working on
implementing path profiling into LLVM. I have completed my project
and would like to submit it.
We are looking for a reviewer for the path profiling implementation. We
have sent previous requests to the llvmdev list but have so far been
unsuccessful.
Please see the attached
2013 Sep 13
2
[LLVMdev] Removing legacy profiling code from LLVM
...this code being here.
If anything, this code is actively confusing those efforts and so I would
like to garbage collect and help pave the way for new stuff. We can always
recover this code from the VCS if needed in the future.
Files on the chopping block:
# deleted: include/llvm/Analysis/PathNumbering.h
# deleted: include/llvm/Analysis/PathProfileInfo.h
# deleted: include/llvm/Analysis/ProfileDataLoader.h
# deleted: include/llvm/Analysis/ProfileDataTypes.h
# deleted: include/llvm/Analysis/ProfileInfo.h
# deleted: include/llvm/Analysis/ProfileInfoLo...
2013 Sep 13
0
[LLVMdev] Removing legacy profiling code from LLVM
...f anything, this code is actively confusing those efforts and so I would
> like to garbage collect and help pave the way for new stuff. We can always
> recover this code from the VCS if needed in the future.
>
> Files on the chopping block:
> # deleted: include/llvm/Analysis/PathNumbering.h
> # deleted: include/llvm/Analysis/PathProfileInfo.h
> # deleted: include/llvm/Analysis/ProfileDataLoader.h
> # deleted: include/llvm/Analysis/ProfileDataTypes.h
> # deleted: include/llvm/Analysis/ProfileInfo.h
> # deleted: include/ll...