search for: looptest

Displaying 20 results from an estimated 20 matches for "looptest".

Did you mean: loopnest
2010 Feb 16
2
Problem in gdb
...am using /usr/bin/gdb we are not able to hit the break point set. [admin at corviewsecondary ~]$ file /usr/bin/gdb /usr/bin/gdb: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped [admin at corviewsecondary ~]$ /usr/bin/gdb ./loopTest GNU gdb Red Hat Linux (6.3.0.0-1.132.EL4rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions....
2006 Jan 29
0
strange performance issue
hi i just setup a test with asterisk 1.2 to see how many concurrent calls it could handle, and I came across something quite strange; with ~1000 calls between two asterisk servers, generated with [looptest] exten => _X.,1,GotoIf($[ ${EXTEN} > 1000 ]?pickup:dial) exten => _X.,n(pickup),Answer exten => _X.,n,Echo exten => _X.,n(dial),Dial(SIP/looptest/$[ ${EXTEN} + 1]) ...ping-pong dialing beween two servers. On one of the servers, system- and user load was low and fine, but on the ot...
2006 Mar 19
0
[LLVMdev] Stupid '-load-vn -licm' question (LLVM 1.6)
...diate future. :( After a bit of digging, I found one open bug and two failing test cases, all of which appear to be feature requests: #217: LLVM needs a generic dominator update mechanism nullpointer.ll: "a load or store of a pointer indicates that the pointer is not null." looptest.ll: "Note that this is a "feature" test, not a correctness test." All the other test cases pass, and none of the other unassigned bugs mention CEE. (I checked Bugzilla by hand--since searching for "correlated" doesn't even find bug #217--so I might have miss...
2011 Apr 28
1
Trying to perform an inner loop a random number of times
Grateful for any hints as to why I'm not getting the inner loop to cycle the expected number of times. Code and one run's results below. Thanks, Galen > # source("looptest.r") > sp<-numeric() > iter<-numeric() > rn<-numeric() > ds<-data.frame(sp, iter, rn) > > for (sp in c(1:6)) { + i<-1 + while (i <= 5) { + rn<-0 + rn<-round(runif(1, 1, 5)) +...
2006 Mar 17
2
[LLVMdev] Stupid '-load-vn -licm' question (LLVM 1.6)
On Fri, 17 Mar 2006, Eric Kidd wrote: >> I'm particularly confused by the rlwinm instructions that keep turning up >> in PowerPC output, and the double test against 98. I don't have a problem >> or anything; I'm just trying to figure out what's going on. :-) > > Ah! The backend is running -lowerswitch, which does a binary search of the > case labels
2011 Jul 29
2
[LLVMdev] sys::getHostTriple failed to recognize ARM correctly
...'/nfs_home/chenwj/test/native-build/arm2/Debug+Asserts/bin/lli' '/nfs_home/chenwj/test/llvm/test/ExecutionEngine/2003-01-04-ArgumentBug.ll' > '/dev/null' -- ******************** Testing: 0 .. 10.. 20.. 30.. 40.. 50 FAIL: LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll (3174 of 6030) ******************** TEST 'LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll' FAILED ******************** Script: -- /nfs_home/chenwj/test/native-build/arm2/Debug+Asserts/bin/lli /nfs_home/chenwj/test/llvm/test/ExecutionEngine/2003-01-04-LoopTest.ll > /dev/null -- Exit Cod...
2011 Nov 04
7
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...working when the target is specified to be different than host: in the following list of failing testcases I see the JIT cases failing: Failing Tests (26): LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: Execu...
2012 Jun 19
2
[LLVMdev] mc jit
...> make check-all LIT_ARGS=--param=jit_impl=mcjit Thanks. When I run this on x86 ubuntu, there are 47 failures. Failing Tests (47): LLVM :: ExecutionEngine/MCJIT/2002-12-16-ArgTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll LLVM :: ExecutionEngine/MCJIT/2003-01-04-LoopTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-04-PhiTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-09-SARTest.ll LLVM :: ExecutionEngine/MCJIT/2003-01-10-FUCOM.ll LLVM :: ExecutionEngine/MCJIT/2003-01-15-AlignmentTest.ll LLVM :: ExecutionEngine/MCJIT/2003-05-06-LivenessClobber.ll...
2011 Nov 04
0
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...specified to be different than host: in the > following list of failing testcases I see the JIT cases failing: > > Failing Tests (26): >    LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll >    LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll >    LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll >    LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll >    LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll >    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >    LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion....
2010 Mar 31
0
[LLVMdev] LoopInfo fails
Hi! if I have this little function: float loopTest(float a, float b) { float x = 1.0f; int i = 0; if (a < b) goto l; for (i = 0; i < 10; ++i) { x *= a; l: x += b; } return x; } then llvm::LoopInfo does not detect that there is a loop. Is this a bug or is such a case not allowed?...
2010 Mar 31
0
[LLVMdev] LoopInfo fails
On 03/31/10 17:12, Jochen Wilhelmy wrote: > Hi! > > if I have this little function: > > float loopTest(float a, float b) > { > float x = 1.0f; > int i = 0; > if (a< b) > goto l; > for (i = 0; i< 10; ++i) > { > x *= a; > l: > x += b; > } > return x; > } > > then llvm::LoopInfo...
2003 Apr 01
7
Line is stuck off hook...
Greetings, I am running Asterisk with a T100P and a Zhone channel bank for over a month now. For the most part it works fine but from time to time (about once a week) the system will not let go of a line and will play the greeting over and over. Anyone calling gets a busy signal. If I reset Asterisk everything works fine. Has anyone seen this problem before and fixed it? If so what did you do?
2012 Jun 19
0
[LLVMdev] mc jit
On Mon, Jun 18, 2012 at 04:56:53PM -0700, reed kotler wrote: > I don't see any tests in either test or test-suite for -use-mcjit. For ARM, we need to manually switch to use mcjit, say $ make check-all LIT_ARGS=--param=jit_impl=mcjit Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799
2012 Jun 19
0
[LLVMdev] mc jit
...impl=mcjit > Thanks. > > When I run this on x86 ubuntu, there are 47 failures. > > Failing Tests (47): > LLVM :: ExecutionEngine/MCJIT/2002-12-16-ArgTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-04-LoopTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-04-PhiTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-09-SARTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-10-FUCOM.ll > LLVM :: ExecutionEngine/MCJIT/2003-01-15-AlignmentTest.ll > LLVM :: ExecutionEngine/MCJIT...
2012 Mar 27
0
[LLVMdev] [cfe-dev] Announcing 3.1 Release Branch Date!
Le mardi 27 mars 2012 à 14:36 -0700, Bill Wendling a écrit : > IMPORTANT! IMPORTANT! IMPORTANT! > [...] > By the way, we are looking for ARM testers. There was a lot of interest in the 3.0 release for an ARM release. We will try to do one this release on a trial basis. We are looking for ARMv7 cortex-a8 and cortex-a9 on Linux. If you are interested, I can upload the current trunk
2011 Nov 04
1
[LLVMdev] JIT should query host info at runtime - Re: buildbot failure in LLVM on llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
...nt than host: in the >> following list of failing testcases I see the JIT cases failing: >> >> Failing Tests (26): >>    LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll >>    LLVM :: ExecutionEngine/2003-01-04-ArgumentBug.ll >>    LLVM :: ExecutionEngine/2003-01-04-LoopTest.ll >>    LLVM :: ExecutionEngine/2003-01-15-AlignmentTest.ll >>    LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll >>    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >>    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >>    LLVM :: ExecutionEngine/2003-08...
2012 Jun 18
4
[LLVMdev] mc jit
I don't see any tests in either test or test-suite for -use-mcjit. Are we not testing this yet? There are lots of other llc options. What is our plan for testing these?
2012 Mar 27
5
[LLVMdev] Announcing 3.1 Release Branch Date!
IMPORTANT! IMPORTANT! IMPORTANT! We will be branching for the 3.1 release on April 16th! :-) This gives us a little over two weeks to get the trees into the most stable condition we can. What this means for you: All major features for the 3.1 release should be finished or near completion by the April 16th. After April 16th, we will accept only bug fixes and patches which do not change the
2011 Dec 15
2
[LLVMdev] llvm/clang test failures on powerpc-darwin8
...oadstore.ll LLVM : : CodeGen/PowerPC/vec_misaligned.ll LLVM : : CodeGen/PowerPC/vec_splat_constant.ll LLVM : : DebugInfo/array.ll LLVM : : ExecutionEngine/2002-12-16-ArgTest.ll LLVM : : ExecutionEngine/2003-01-04-ArgumentBug.ll LLVM : : ExecutionEngine/2003-01-04-LoopTest.ll LLVM : : ExecutionEngine/2003-01-04-PhiTest.ll LLVM : : ExecutionEngine/2003-01-09-SARTest.ll LLVM : : ExecutionEngine/2003-01-10-FUCOM.ll LLVM : : ExecutionEngine/2003-01-15-AlignmentTest.ll LLVM : : ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM : : Exec...
2009 Feb 23
1
[LLVMdev] 2.5 Pre-release2 available for testing
On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to