Displaying 8 results from an estimated 8 matches for "printal".
Did you mean:
print_l
2007 Jun 17
2
Branch 'as' - test/trace
...riables:
+// - "values": The array of values to be checked
+// - "names": The array of corresponding string representations for values.
+// It's suggested to use these instead of using values directly to
+// avoid spurious toString and valueOf calls.
+
+printall = new Object ();
+printall.valueOf = function () {
+ trace ("valueOf called");
+ return this;
+};
+printall.toString = function () {
+ trace ("toString called");
+ return this;
+};
+
+tostring = new Object ();
+tostring.toString = function () {
+ trace ("toString call...
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 t...
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.
...anagers
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 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 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.
...nything, 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 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::Cr...
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.
...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 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::CreateInfoOutputFi...
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.
...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 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
>&...
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
...ring to printvalueof and printtostring in values.as
To avoid non-determinism with having multiple variables using different case
diff --git a/test/trace/values.as b/test/trace/values.as
index 25afaea..b7759c7 100644
--- a/test/trace/values.as
+++ b/test/trace/values.as
@@ -16,14 +16,14 @@ printall.toString = function () {
return this;
};
-tostring = new Object ();
-tostring.toString = function () {
+printtostring = new Object ();
+printtostring.toString = function () {
trace ("toString called with " + arguments);
return this;
};
-valueof = new Object ();
-valueof.va...