search for: couman

Displaying 9 results from an estimated 9 matches for "couman".

Did you mean: corman
2010 Jan 05
4
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
...[LLVMdev] Help adding the Bullet physics sdk benchmark to > the LLVM test suite? > To: llvmdev at cs.uiuc.edu > Message-ID: <201001042024.23451.dag at cray.com> > Content-Type: text/plain; charset="iso-8859-15" > > On Monday 04 January 2010 20:11, Erwin Coumans wrote: > > Hi Anton, and happy new year all, > > > > >>One questions though: is it possible to "verify" the results of all > > >>the computations somehow? > > > > Good point, and there is no automated way currently, but we can work on >...
2009 Dec 18
0
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
On Dec 15, 2009, at 5:15 PM, Erwin Coumans wrote: > The linux builds are not using SSE right now, but the vector data is > 16-byte aligned on all platforms. > So if you port this SSE code to another platform (Linux, Altivec, > NEON), you could contribute it back to Bullet? > The most interesting SSE part is the innerloop of...
2004 Sep 24
0
Client can't boot
...R from 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:49 master dhcpd: DHCPOFFER on 10.0.0.150 to 00:0c:76:e7:7b:e2 via eth1 The DHCP server seems to be working correctly, since I can connect another computer and it DHCPACKS the request. Any suggestions? Thanks in advance! -- Groeten/Greetings, Jeroen Coumans www.jeroencoumans.nl
2010 Jan 05
0
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
On Tuesday 05 January 2010 14:53, Erwin Coumans wrote: > How do other benchmarks deal with unstable algorithms or differences in > floating point results? > > >> haven't been following this thread, but this sounds like a typical > >> unstable algorithm problem. Are you always operating that close to > >>...
2010 Jan 05
1
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
Hi Anton, and happy new year all, >>One questions though: is it possible to "verify" the results of all >>the computations somehow? Good point, and there is no automated way currently, but we can work on that. Note that simulation suffers from the 'butterfly effect', so the smallest change anywhere, (cpu, compiler etc) diverges into totally different results after a
2009 Dec 16
4
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
The linux builds are not using SSE right now, but the vector data is 16-byte aligned on all platforms. So if you port this SSE code to another platform (Linux, Altivec, NEON), you could contribute it back to Bullet? The most interesting SSE part is the innerloop of the constraint solver: http://tinyurl.com/ydoapct Some developers replaced some linear algebra functions (in Bullet/LinearMath) with
2010 Jan 05
1
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
We haven't determined what 'failing' means or what the 'correct' behaviour is. Imagine a ball at the top of a rounded hill. If the ball is not exactly at the top but a tiny amount on the left it will roll left, but a tiny amount on the right it will roll right. The difference in initial position can be negligible but the final result is miles away. Is there a irc channel or
2009 Dec 15
2
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
Hi, We are developing the open source Bullet physics engine, used by game and movie studios, and compiler performance tuning is important to us. See http://bullet.googlecode.com The physics engine includes collision detection, rigid body dynamics and soft body dynamics. I've been following the LLVM project for a while, and it seems the Clang C++ compiler is mature enough to compile our
2009 Dec 16
6
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
Hi Anton, Thanks a lot for offering help. Bullet uses basic linear algebra with 4-way vectors, quaternion and matrices. Although most of this is plain portable C++ perhaps LLVM can auto-vectorize some of this? There is a little bit of hand optimized x86 SSE code. This is only enabled on 32bit Windows and Mac OSX Intel builds. >> Should I just use the 2.75 release? If you are interested,