Displaying 5 results from an estimated 5 matches for "timinginfo".
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.
Thanks for the reply! Unfortunately, that seems to have the same
effect as setting llvm::TimePassesIsEnabled myself, and all my same
problems still apply as the TimingInfo's destructor (PassManager.cpp)
is still never called. Running it in the debugger shows that
TimerGroup's removeTimer method is never called, nor is it's
destructor (but it's constructor is).
On Wed, Jun 1, 2011 at 11:51 AM, Andrew Clinton <andrew at sidefx.com> wrote:
> I...
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.
...called in it's destructor) appears to
print everything out to the info-output-file (stderr) when its Timers
are all removed but I see no output, however I'm able to call
llvm::CreateInfoOutputFile myself, pipe to it, and stuff shows up on
stderr. In PassManager.cpp, TheTimeInfo (which is a TimingInfo), gets
assigned once, and as far as I can tell never gets deleted, thus its
destructor is never called, the Timers are never deleted, and the
timing data is never output. Valgrind shows these Timers, TimerGroup,
and TimingInfo as being memory leaks for my application when I enable
llvm::TimePassesI...
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.
Oh, you probably also need to create a static llvm_shutdown_obj.
On 06/01/2011 02:19 PM, Michael Ilseman wrote:
> Thanks for the reply! Unfortunately, that seems to have the same
> effect as setting llvm::TimePassesIsEnabled myself, and all my same
> problems still apply as the TimingInfo's destructor (PassManager.cpp)
> is still never called. Running it in the debugger shows that
> TimerGroup's removeTimer method is never called, nor is it's
> destructor (but it's constructor is).
>
> On Wed, Jun 1, 2011 at 11:51 AM, Andrew Clinton<andrew at sidefx...
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.
...destructor) appears to
> print everything out to the info-output-file (stderr) when its Timers
> are all removed but I see no output, however I'm able to call
> llvm::CreateInfoOutputFile myself, pipe to it, and stuff shows up on
> stderr. In PassManager.cpp, TheTimeInfo (which is a TimingInfo), gets
> assigned once, and as far as I can tell never gets deleted, thus its
> destructor is never called, the Timers are never deleted, and the
> timing data is never output. Valgrind shows these Timers, TimerGroup,
> and TimingInfo as being memory leaks for my application when I enab...
2006 May 09
1
[LLVMdev] Memory leaks in LLVM
...llvm::Pass*
const, llvm::Timer> > >::clear() (stl_tree.h:847)
==10132== by 0x851E94C: std::map<llvm::Pass*, llvm::Timer,
std::less<llvm::Pass*>, std::allocator<std::pair<llvm::Pass* const,
llvm::Timer> > >::clear() (stl_map.h:439)
==10132== by 0x851C0B5: llvm::TimingInfo::~TimingInfo() ( PassManagerT.h
:100)
==10132== by 0x84B0572: __tcf_1 (Pass.cpp:133)
==10132== by 0x4169DEF: exit (in /lib/tls/libc.so.6)
==10132== by 0x4154E89: (below main) (in /lib/tls/libc.so.6)
==10132==
==10132==
==10132== 12 bytes in 1 blocks are still reachable in loss record 3 of...