Displaying 8 results from an estimated 8 matches for "printale".
Did you mean:
printable
2007 Jun 17
2
Branch 'as' - test/trace
test/trace/Makefile.am | 1
test/trace/values.as | 63 +++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 64 insertions(+)
New commits:
diff-tree aaca94203d8a0ccb8feb32c0d57df3401fca0350 (from 987074e275ac77f8799e5fdf41890e8ef126b291)
Author: Benjamin Otte <otte at gnome.org>
Date: Sun Jun 17 12:56:42 2007 +0200
add values.as which provides some default values
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
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.
I have some PassManagers, and I would like to output timing data for
how long each pass takes to execute with a separate 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
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
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.
I got it working with this:
int argc = 2;
const char *argv[2] = {"myopt", "-time-passes"};
cl::ParseCommandLineOptions(argc, (char **)argv, "my optimizer");
On 06/01/2011 01:19 PM, Michael Ilseman wrote:
> I have some PassManagers, and I would like to output timing data for
> how long each pass takes to execute with a separate
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
2007 Jun 01
6
PATCH: Use name instead of pid in QEMU logs
The attached patch changes the logfile name generated by qemu-dm to use the
pattern qemu-dm-[NAME].log instead of qemu-dm-[PID].log. This makes it
easier for the adminsitrator to figure out which log corresponds to which
guest (particularly after a crash where you no long know what PID the
qemu-dm process for your guest had). It also prevents the number of log
files from growing unbounded.
2007 Sep 12
0
9 commits - libswfdec/swfdec_as_function.c libswfdec/swfdec_as_initialize.as libswfdec/swfdec_as_initialize.h libswfdec/swfdec_as_object.c libswfdec/swfdec_as_strings.c libswfdec/swfdec_player_as.c test/trace
libswfdec/swfdec_as_function.c | 11
libswfdec/swfdec_as_initialize.as | 4
libswfdec/swfdec_as_initialize.h | 311 ++++++++++++++--------------
libswfdec/swfdec_as_object.c | 73 ++++--
libswfdec/swfdec_as_strings.c | 1
libswfdec/swfdec_player_as.c | 15 +
test/trace/Makefile.am |