Displaying 5 results from an estimated 5 matches for "thetimeinfo".
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.
...'s removeTimer (also 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 e...
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.
...t'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 memo...
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.
...also 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...
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.
...or) 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 TimingIn...
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...t;llvm::PrintBeforeAll"},
{"_ZN4llvmL13PrintAfterAllE", "llvm::PrintAfterAll"},
{"_ZN12_GLOBAL__N_1L15TimingInfoMutexE", "(anonymous namespace)::TimingInfoMutex"},
{"_ZL12EnableTiming", "EnableTiming"},
{"_ZL11TheTimeInfo", "TheTimeInfo"},
{"_ZL15PassRegistryObj", "PassRegistryObj"},
{"_ZL4Lock", "Lock"},
{"_ZL8MoreHelp", "MoreHelp"},
{"_ZL20RegisteredOptionList", "RegisteredOptionList"},
{"_Z...