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 Benchmarking Platform
Phoromatic Test Orchestration

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 News
  1. VirtualBox 5.0 RC3 Brings VMM Fixes, Takes Care Of Some KDE DnD Problems
  2. Ubuntu Is Finally Fixing Its Annoying GRUB Setting
  3. Firefox 39.0 Brings New Features, HTML5 Changes
  4. OPNsense 15.7 Released As Fork Of Pfsense
  5. The Less-Powerful Intel Compute Stick With Ubuntu Will Soon Ship
  6. Kodi 15.0 Release Candidate 1 Arrives
  7. Fedora 23: Python 3 Default Approved; Netizen Spin Rejected
  8. GNOME Shell & Mutter Just Landed More Wayland Improvements
  9. Ubuntu MATE Announces A Partnership With A PC Hardware Vendor
  10. Linux 4, GCC v. Clang & Vulkan Were Among The Hot Stories So Far This Year
Latest Articles & Reviews
  1. 6-Way File-System Comparison On The Linux 4.1 Kernel
  2. How KDE VDG Is Trying To Make Open-Source Software Beautiful
  3. Attempting To Try Out BCache On The Linux 4.1 Kernel
  4. CompuLab's Fitlet Is A Very Tiny, Fanless, Linux PC With AMD A10 Micro
Most Viewed News This Week
  1. Kubuntu 15.10 Could Be The End Of The Road
  2. KDBUS Won't Be Pushed Until The Linux 4.3 Kernel
  3. Pinos Is For Linux Video What PulseAudio Is For Audio
  4. The State & Complications Of Porting The Unity Editor To Linux
  5. The Staging Pull For Linux 4.2: "Big, Really Big"
  6. Latest Rumor Pegs Microsoft Wanting To Buy AMD
  7. "PulseVideo" Coming To Complement PulseAudio?
  8. Exciting Features Merged So Far For The Linux 4.2 Kernel