search for: scimark2

The release of a new code generator in Mono 2.2 prompted me to benchmark the performance of various VMs using the SciMark2 benchmark on an 8x 2.1GHz 64-bit Opteron and I have published the results here: http://flyingfrogblog.blogspot.com/2009/01/mono-22.html The LLVM results were generated using llvm-gcc 4.2.1 on the C version of SciMark2 with the following command-line options: llvm-gcc -Wall -lm -O2 -funroll...

I just remembered an anomalous result that I stumbled upon whilst tweaking the command-line options to llvm-gcc. Specifically, the -msse3 flag does a great job improving the performance of floating point intensive code on the SciMark2 benchmark but it also degrades the performance of the int-intensive Monte Carlo part of the test: $ llvm-gcc -Wall -lm -O3 *.c -o scimark2 $ ./scimark2 Using 2.00 seconds min time per kenel. Composite Score: 432.84 FFT Mflops: 358.90 (N=1024) SOR Mflops...

I am seeing the same problems using 'llvm-ld' with llvm-gcc at -O4 on x86_64 Fedora 8 linux as on Darwin. Another example of this is building the scimark2_1c benchmark... http://math.nist.gov/scimark2/download_c.html as follows on x86_64 Fedora 8... /home/howarth/llvm-gcc42-work/bin/gcc -O4 -m64 -c FFT.c /home/howarth/llvm-gcc42-work/bin/gcc -O4 -m64 -c kernel.c /home/howarth/llvm-gcc42-work/bin/gcc -O4 -m64 -c Stopwatch.c /home/howarth/llvm-gc...

...; wrote: > > I just remembered an anomalous result that I stumbled upon whilst > > tweaking the command-line options to llvm-gcc. Specifically, the -msse3 > > flag > > The -msse3 flag? Does the -msse2 flag have a similar effect? Yes: $ llvm-gcc -Wall -lm -O3 -msse2 *.c -o scimark2 $ ./scimark2 Composite Score: 525.99 FFT Mflops: 538.35 (N=1024) SOR Mflops: 472.29 (100 x 100) MonteCarlo: Mflops: 120.92 Sparse matmult Mflops: 585.14 (N=1000, nz=5000) LU Mflops: 913.27 (M=100, N=100) But -msse does not:...

...ile LLVM, as it is using C code, it is taking advantage of memory allocation by hand. On Fri, Jan 30, 2009 at 9:56 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > > The release of a new code generator in Mono 2.2 prompted me to benchmark the > performance of various VMs using the SciMark2 benchmark on an 8x 2.1GHz > 64-bit Opteron and I have published the results here: > > http://flyingfrogblog.blogspot.com/2009/01/mono-22.html > > The LLVM results were generated using llvm-gcc 4.2.1 on the C version of > SciMark2 with the following command-line options: > >...

...2017 at 18:54, Diana Picus <diana.picus at linaro.org <mailto:diana.picus at linaro.org>> wrote: >> Hi all, >> >> I added a buildbot [1] running the test-suite with -O0 -global-isel. It runs into the same 2 timeouts that I reported previously on this thread (paq8p and scimark2). It would be nice to make it green before flipping the switch. >> >> >> I did some more investigations on a machine similar to the one running the buildbot. For paq8p and scimark2, I get these results for O0: >> >> PAQ8p: >> Fast isel: 666.344 >> Global...

...4, Diana Picus <diana.picus at linaro.org <mailto:diana.picus at linaro.org>> wrote: >>> Hi all, >>> >>> I added a buildbot [1] running the test-suite with -O0 -global-isel. It runs into the same 2 timeouts that I reported previously on this thread (paq8p and scimark2). It would be nice to make it green before flipping the switch. >>> >>> >>> I did some more investigations on a machine similar to the one running the buildbot. For paq8p and scimark2, I get these results for O0: >>> >>> PAQ8p: >>> Fast isel:...

On 12 June 2017 at 18:54, Diana Picus <diana.picus at linaro.org> wrote: > Hi all, > > I added a buildbot [1] running the test-suite with -O0 -global-isel. It > runs into the same 2 timeouts that I reported previously on this thread > (paq8p and scimark2). It would be nice to make it green before flipping the > switch. > > I did some more investigations on a machine similar to the one running the buildbot. For paq8p and scimark2, I get these results for O0: PAQ8p: Fast isel: 666.344 Global isel: 731.384 SciMark2-C: Fast isel: 463.908 Glo...

...; To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Saturday, January 31, 2009 6:56 AM Subject: [LLVMdev] Performance vs other VMs > > The release of a new code generator in Mono 2.2 prompted me to benchmark > the > performance of various VMs using the SciMark2 benchmark on an 8x 2.1GHz > 64-bit Opteron and I have published the results here: > > http://flyingfrogblog.blogspot.com/2009/01/mono-22.html > > The LLVM results were generated using llvm-gcc 4.2.1 on the C version of > SciMark2 with the following command-line options: > >...

On 4 April 2017 at 06:55, Diana Picus via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On the test-suite, we get 2 timeouts during execution (paq8p and > scimark2). Interesting. I'd not seen those failures in the configurations I'd run. I'll look into them (other than that my best bet for debugging is a kernel panic, this has to be easier!). > On the test-suite, we get 2 timeouts during execution (paq8p and > scimark2). Other than that, e...

On Fri, Jan 30, 2009 at 5:43 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > > I just remembered an anomalous result that I stumbled upon whilst tweaking the > command-line options to llvm-gcc. Specifically, the -msse3 flag The -msse3 flag? Does the -msse2 flag have a similar effect? -Eli

...>> wrote: On 12 June 2017 at 18:54, Diana Picus <diana.picus at linaro.org<mailto:diana.picus at linaro.org>> wrote: Hi all, I added a buildbot [1] running the test-suite with -O0 -global-isel. It runs into the same 2 timeouts that I reported previously on this thread (paq8p and scimark2). It would be nice to make it green before flipping the switch. I did some more investigations on a machine similar to the one running the buildbot. For paq8p and scimark2, I get these results for O0: PAQ8p: Fast isel: 666.344 Global isel: 731.384 SciMark2-C: Fast isel: 463.908 Global isel: 496...

...ebruary 2009 05:25:40 Ramón García wrote: > This is not a quite fair comparison. Other virtual machines must be > doing garbage collection, while LLVM, as it is using C code, it is > taking advantage of memory allocation by hand. That is an insignificant advantage in this particular case (SciMark2) because the memory for each test is preallocated and not part of the measurement and the heap and stack are both tiny during the computations so there is little to traverse. I am interested in the comparative results for LLVM because I consider it to represent how fast my LLVM-based VM might...

...s/ Of particular note was his use of SciMark 2.0 which is a NIST developed benchmark for scientific computing. Its available in both java and C and computes a MFLOPS number. It would be good to include this in our test suite if we can (hint, hint, John). You can find it here: http://math.nist.gov/scimark2/index.html Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040921/016665c8/attachmen...

Hi all, I added a buildbot [1] running the test-suite with -O0 -global-isel. It runs into the same 2 timeouts that I reported previously on this thread (paq8p and scimark2). It would be nice to make it green before flipping the switch. At the moment, it lives in an internal buildmaster that I've setup for this purpose. If we fix it and it proves to be stable for a week or two, I'll move it to the public master. Cheers, Diana [1] http://master2.llvm.validat...

Thanks Kristof. Sounds like we'll need to investigate though I'd say it is not blocking the switch. At this point I think everybody is on board to flip the switch. @Eric, how does that sound to you? Thanks, Q > Le 1 juin 2017 à 07:46, Kristof Beyls <Kristof.Beyls at arm.com> a écrit : > > >> On 31 May 2017, at 17:07, Quentin Colombet <qcolombet at

...>> wrote: On 12 June 2017 at 18:54, Diana Picus <diana.picus at linaro.org<mailto:diana.picus at linaro.org>> wrote: Hi all, I added a buildbot [1] running the test-suite with -O0 -global-isel. It runs into the same 2 timeouts that I reported previously on this thread (paq8p and scimark2). It would be nice to make it green before flipping the switch. I did some more investigations on a machine similar to the one running the buildbot. For paq8p and scimark2, I get these results for O0: PAQ8p: Fast isel: 666.344 Global isel: 731.384 SciMark2-C: Fast isel: 463.908 Global isel: 496...

All the LLVM lab FNT builders were reporting failures in the same set of tests (scimark2, LivermooreLoops, some others). Now they've all turned green but the same tests are still failing. I don't see any commits to deliberately make the FNT pass, so it looks like someone broke failure detection... Note that the FNT "report" text became empty at the same time. Here...

...ed issues for these tests, can we add them to ignore-list for this builder? It allows faster catch and fix other failures (if we get them). I also wandering, may be some of them just incompatible with freebsd platform, or with CPU they were tested at? Below some details: MultiSource/Benchmarks/SciMark2-C - fp difference. MultiSource/Benchmarks/nbench - timeout. SingleSource/UnitTests, Output/initp1.out-llc - empty stdout. SingleSource/Benchmarks/Misc/mandel - fp difference. After short analysis, I found out, that first 3 tests were disabled on clang-X86_64-freebsd machine. "mandel" t...

...te was his use of SciMark 2.0 which is a NIST developed > benchmark for scientific computing. Its available in both java and C and > computes a MFLOPS number. It would be good to include this in our test > suite if we can (hint, hint, John). You can find it here: > http://math.nist.gov/scimark2/index.html > > Reid. > > > ------------------------------------------------------------------------ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu...