Displaying 7 results from an estimated 7 matches for "profileverifierpass".
2009 Sep 16
1
[LLVMdev] FunctionPass Analysis is not saved after ModulePasses run?
Hi,
I have a problem with the following scenario:
I use the ProfileEstimatorPass to get ProfileInfo and verifiy this info with the ProfileVerifierPass. (Please bear with me, its not about the profiling but about the Pass interaction.) Then the LowerSetJumpPass is executed and I want to verify that the esimtated ProfileInfo survives this pass by calling again the ProfileVerifierPass. This is what it looks like:
No Profile Information
ModulePas...
2009 Sep 16
0
[LLVMdev] FunctionPass Analysis is not saved after ModulePasses run?
Hi,
I have a problem with the following scenario:
I use the ProfileEstimatorPass to get ProfileInfo and verifiy this info with the ProfileVerifierPass. (Please bear with me, its not about the profiling but about the Pass interaction.) Then the LowerSetJumpPass is executed and I want to verify that the esimtated ProfileInfo survives this pass by calling again the ProfileVerifierPass. This is what it looks like:
No Profile Information
ModulePas...
2013 Sep 13
2
[LLVMdev] Removing legacy profiling code from LLVM
...ed: lib/Analysis/ProfileDataLoaderPass.cpp
# deleted: lib/Analysis/ProfileEstimatorPass.cpp
# deleted: lib/Analysis/ProfileInfo.cpp
# deleted: lib/Analysis/ProfileInfoLoader.cpp
# deleted: lib/Analysis/ProfileInfoLoaderPass.cpp
# deleted: lib/Analysis/ProfileVerifierPass.cpp
# deleted: lib/Transforms/Instrumentation/EdgeProfiling.cpp
# deleted: lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp
# deleted: lib/Transforms/Instrumentation/PathProfiling.cpp
Please let me know if you have any concerns. I'm likely to submit this
rathe...
2013 Jul 30
0
[LLVMdev] LLVM (opt) -profile-verifier is not pass resilient
...ter a profile run, I launched OPT with -profile-loader
-profile-verifier flags and also passed -O3 flag. This caused OPT to
give a warning "WARNING: profile information is inconsistent with the
current program!" and then fail with an assert (ASSERT:inWeight and
outWeight do not match
opt: ProfileVerifierPass.cpp:226:
void<unnamed>::ProfileVerifierPassT<FType, BType>::CheckValue(bool,
const char*, <unnamed>::ProfileVerifierPassT<FType,
BType>::DetailedBlockInfo*) [with FType = llvm::Function, BType =
llvm::BasicBlock]: Assertion `0 && (Message)' failed.)
Instead of p...
2013 Sep 13
0
[LLVMdev] Removing legacy profiling code from LLVM
...leDataLoaderPass.cpp
> # deleted: lib/Analysis/ProfileEstimatorPass.cpp
> # deleted: lib/Analysis/ProfileInfo.cpp
> # deleted: lib/Analysis/ProfileInfoLoader.cpp
> # deleted: lib/Analysis/ProfileInfoLoaderPass.cpp
> # deleted: lib/Analysis/ProfileVerifierPass.cpp
> # deleted: lib/Transforms/Instrumentation/EdgeProfiling.cpp
> # deleted: lib/Transforms/Instrumentation/OptimalEdgeProfiling.cpp
> # deleted: lib/Transforms/Instrumentation/PathProfiling.cpp
>
> Please let me know if you have any concerns. I'm lik...
2009 Jun 29
7
[LLVMdev] Profiling in LLVM Patch
...fileEstimatorPass that does an offline estimation of a profile based
on branching and loop depth (also proposed in [Ball94])
(it is possible to use this ProfileEstimator stand-alone to have at least
some profile estimation available in the frontend without doing profiling
runs)
*) a ProfileVerifierPass that checks the current profiling information
against the flow preservation rules
I did performance measurements on the C and C++ portions of the SPEC CPU2000
benchmark, the results are:
*) on average 46% of the edges are instrumented with a counter (in
comparison to 100% with the current...
2009 Jul 01
0
[LLVMdev] Profiling in LLVM Patch
...that does an offline estimation of a profile based
> on branching and loop depth (also proposed in [Ball94])
> (it is possible to use this ProfileEstimator stand-alone to have at least
> some profile estimation available in the frontend without doing profiling
> runs)
> *) a ProfileVerifierPass that checks the current profiling information
> against the flow preservation rules
>
> I did performance measurements on the C and C++ portions of the SPEC CPU2000
> benchmark, the results are:
> *) on average 46% of the edges are instrumented with a counter (in
> comparison...