1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Benchmarking LLVM's Automatic Loop Vectorizer

Compiler

Published on 27 October 2012 08:36 AM EDT
Written by Michael Larabel in Compiler
1 Comment

Yesterday I wrote about an automatic loop vectorizer having been committed to LLVM this week. I've now carried out some benchmarks of this automatic loop vectorizer in conjunction with the Clang compiler to see the performance impact of this still experimental but promising feature.

As mentioned in Friday's article, the LLVM auto loop vectorizer is still deemed experimental and "far from being ready", thus is currently not enabled by default. This feature will premiere with LLVM 3.2 in December and can be enabled by passing the -mllvm -vectorize flags through the Clang C/C++ compiler.

While ultimately the automatic loop vectorizer should be a performance win, one of the Apple engineers working on this LLVM code wrote, "At the moment the vectorizer will vectorize anything it can, because we do not have a 'cost-model' to estimate the profitability of vectorization. Implementing a cost model is a high-priority for us, and until this is ready you should expect to see slowdowns on many loops. Another area which we need to improve is the memory dependence check. At the moment we have a very basic memory legality check which can be improved. Additionally, there are a number of cases where we generate poor vector code or suffer from a phase-rdering problem. Once we solve these problems we can continue to implement additional features."

Using the latest LLVM/Clang SVN code as of Friday, I carried out some early benchmarks of the automatic loop vectorizer when running some open-source Phoronix Test Suite / OpenBenchmarking.org tests. The only difference between test runs was setting the CFLAGS/CXXFLAGS for -mllvm -vectorize.

For some of the benchmarks, there was no measurable change in performance when the automatic loop vectorizer for LLVM was enabled.

The most common case, however, was actually a performance drop when the LLVM auto loop vectorizer was enabled. As mentioned, there isn't yet any cost-model for LLVM to determine when to vectorize a loop or not, plus other performance tuning of this newly-committed code is still needed.

Of the benchmarks run for this initial testing, the only test profile showing a positive improvement out of the automatic loop vectorizer was PostgreSQL.

More benchmarks and other system information/logs from the system during this initial LLVM auto loop vectorizer benchmarking can be found on OpenBenchmarking.org via the 1210264-RA-LLVMLOOPV66 result file.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. MSI X99S SLI PLUS On Linux
  2. NVIDIA GeForce GTX 970 Offers Great Linux Performance
  3. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  4. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
Latest Linux Articles
  1. Open-Source Radeon 2D Performance Is Better With Ubuntu 14.10
  2. RunAbove: A POWER8 Compute Cloud With Offerings Up To 176 Threads
  3. 6-Way Ubuntu 14.10 Linux Desktop Benchmarks
  4. Ubuntu 14.10 XMir System Compositor Benchmarks
Latest Linux News
  1. Sandusky Lee: Great Cabinets For Storing All Your Computer Gear
  2. Fedora 21 Beta & Final Release Slip Further
  3. Mesa 10.3.2 Has A Couple Bug-Fixes
  4. RadeonSI/R600g HyperZ Support Gets Turned Back On
  5. openSUSE Factory & Tumbleweed Are Merging
  6. More Fedora Delays: Fedora 21 Beta Slips
  7. Mono Brings C# To The Unreal Engine 4
  8. Coreboot Now Has Support For Intel Broadwell Hardware
  9. Enlightenment's EFL 1.12 Alpha Has Evas GL-DRM Engine, OpenGL ES 1.1 Support
  10. GTK+ Lands Experimental Backend For Mir Display Server
Latest Forum Discussions
  1. Debian Is Back To Discussing Init Systems, Freedom of Choice
  2. AMD Radeon VDPAU Video Performance With Gallium3D
  3. HOPE: The Ease Of Python With The Speed Of C++
  4. Updated and Optimized Ubuntu Free Graphics Drivers
  5. Ubuntu 16.04 Might Be The Distribution's Last 32-Bit Release
  6. Linux hacker compares Solaris kernel code:
  7. Advertisements On Phoronix
  8. Users/Developers Threatening Fork Of Debian GNU/Linux