Displaying 6 results from an estimated 6 matches for "67ms".
Did you mean:
60ms
2010 Sep 05
2
Windows 7 64-bit clients with high latency
Hi,
Windows 7 64-bit clients have a very high latency (constantly rising) using of tinc. 32-bit clients are working with normal speed.
Does anyone have a solution for this problem?
Viele Gr??e
Dirk Krause
2016 Jan 24
4
Skip redundant checks in AliasSet::aliasesUnknownInst
...one could review me, I
would try to implement it. A temporary patch can be found attached
(for example, ViewedInst can become a second parameter of
AliasSetTracker::addUnknown ). It
passes the LLVM regression tests and helps to reduce the runtime of
'opt -basicaa -licm out.opt.ll’ from 130ms to 67ms and the runtime of
'opt -basicaa -licm out.opt2.ll’ from 117ms to 62ms (out.opt.ll and
out.opt2.ll can be found on the following link
https://llvm.org/bugs/show_bug.cgi?id=23077).
Thank you for the attention!
--
Cheers, Roman Gareev.
-------------- next pa...
2009 Apr 27
4
dtrace : isolating the slow write
...27
33554432 | 23
67108864 | 5
134217728 | 0
If you look at the statistics value for the second last interval, the value is 5 writes for 67ms. There are instances when the statistic is spoiled by just few writes like this.
My question related to this is " can we isolate why this write is taking so much time?" or "can we isolate during which write this data was seen?"
--
This message posted from opensolaris.org
2016 Jan 27
2
Skip redundant checks in AliasSet::aliasesUnknownInst
...implement it. A temporary patch can be found attached
>> (for example, ViewedInst can become a second parameter of
>> AliasSetTracker::addUnknown ). It
>> passes the LLVM regression tests and helps to reduce the runtime of
>> 'opt -basicaa -licm out.opt.ll’ from 130ms to 67ms and the runtime of
>> 'opt -basicaa -licm out.opt2.ll’ from 117ms to 62ms (out.opt.ll and
>> out.opt2.ll can be found on the following link
>> https://llvm.org/bugs/show_bug.cgi?id=23077).
>>
>> Thank you for the attention!
>>
>> --
>>...
2015 Dec 12
2
Objects of MemoryLocation class are created for ‘llvm.memset.*‘ intrinsics
2015-12-11 23:44 GMT+05:00 Hal Finkel <hfinkel at anl.gov>:
> Hi Roman,
>
> The MemoryLocation objects are involved in findAliasSetForUnknownInst, but none are created there for the memset intrinsic. MemoryLocation objects are only involved for the regular memory accesses being compared to the unknown instruction. See AliasSet::aliasesUnknownInst in lib/Analysis/AliasSetTracker.cpp.
2016 Jan 27
2
Skip redundant checks in AliasSet::aliasesUnknownInst
...be found attached
> >> (for example, ViewedInst can become a second parameter of
> >> AliasSetTracker::addUnknown ). It
> >> passes the LLVM regression tests and helps to reduce the runtime of
> >> 'opt -basicaa -licm out.opt.ll’ from 130ms to 67ms and the
> runtime of
> >> 'opt -basicaa -licm out.opt2.ll’ from 117ms to 62ms (out.opt.ll and
> >> out.opt2.ll can be found on the following link
> >> https://llvm.org/bugs/show_bug.cgi?id=23077).
> >>
> >> Thank you for th...