search for: timergroups

Displaying 7 results from an estimated 7 matches for "timergroups".

Did you mean: timergroup
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
2011 Jun 01
2
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
...rate application using the API, rather than through an llvm tool. Unfortunately, I'm having trouble seeing how to use the existing facilities without using opt. Setting llvm::TimePassesIsEnabled before creating the PassManagers doesn't seem to output anything, though it is making Timers and TimerGroups. Even if I call llvm::getPassTimer for one of the passes (and I do get a timer that is initialized), I can't figure out to get to its TimerGroup (TG is private, but if I use a debugger, I can get it and call printAll successfully). Looking through the code, TimerGroup's removeTimer (also ca...
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
2011 Jun 01
2
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
...er than through an llvm tool. Unfortunately, I'm having >> trouble seeing how to use the existing facilities without using opt. >> Setting llvm::TimePassesIsEnabled before creating the PassManagers >> doesn't seem to output anything, though it is making Timers and >> TimerGroups. Even if I call llvm::getPassTimer for one of the passes >> (and I do get a timer that is initialized), I can't figure out to get >> to its TimerGroup (TG is private, but if I use a debugger, I can get >> it and call printAll successfully). Looking through the code, >> T...
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
2011 Jun 01
0
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
...t; the API, rather than through an llvm tool. Unfortunately, I'm having > trouble seeing how to use the existing facilities without using opt. > Setting llvm::TimePassesIsEnabled before creating the PassManagers > doesn't seem to output anything, though it is making Timers and > TimerGroups. Even if I call llvm::getPassTimer for one of the passes > (and I do get a timer that is initialized), I can't figure out to get > to its TimerGroup (TG is private, but if I use a debugger, I can get > it and call printAll successfully). Looking through the code, > TimerGroup's...
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
2011 Jun 01
0
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
...an llvm tool. Unfortunately, I'm having >>> trouble seeing how to use the existing facilities without using opt. >>> Setting llvm::TimePassesIsEnabled before creating the PassManagers >>> doesn't seem to output anything, though it is making Timers and >>> TimerGroups. Even if I call llvm::getPassTimer for one of the passes >>> (and I do get a timer that is initialized), I can't figure out to get >>> to its TimerGroup (TG is private, but if I use a debugger, I can get >>> it and call printAll successfully). Looking through the code...
[LLVMdev] generating pass timing info in a JIT context
2012 Jun 13
0
[LLVMdev] generating pass timing info in a JIT context
Our project runs LLVM in a JIT context, and we want to explore where the time is being spent in the various LLVM components. At the moment, we're running with a production version of 3.0, and expecting to upgrade to 3.1 soon. We noticed that clang and llc can display component timing using the -ftime-passes and -time-passes options respectively. A little poking around in the code revealed
printing statistics timers
2018 Feb 07
1
printing statistics timers
Hi, The code in Support/Timer.cpp has strangely inconsistent behavior for printAll vs printJSONValues. The former can work multiple times, while the latter calls prepareToPrintList(), which stops all timers, hence making all further attempts to print timers crash. Would it be possible not to call prepareToPrintList on printJSONValues, or at least make it optional? I am trying to serialize
[LLVMdev] Memory leaks in LLVM
2006 May 09
1
[LLVMdev] Memory leaks in LLVM
Hi, Probably some of the leaks Valgrind reports are spurious, but the numbers seem to be significant enough to demand some attention: ==10132== LEAK SUMMARY: ==10132== definitely lost: 15,624 bytes in 558 blocks. ==10132== indirectly lost: 44,548 bytes in 1,591 blocks. ==10132== possibly lost: 37,576 bytes in 98 blocks. ==10132== still reachable: 1,336,876 bytes in 1,364 blocks.