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

LLVM May Expand Its Use Of The Loop Vectorizer

Compiler

Published on 06 June 2013 01:05 AM EDT
Written by Michael Larabel in Compiler
8 Comments

LLVM's Loop Vectorizer, which is able to automatically vectorize code loops for performance benefits in many scenarios, may find its use expanded for other optimization levels in future LLVM releases.

LLVM's automatic loop vectorizer was merged for the LLVM 3.2 release and benchmarking the loop vectorizer showed it to provide performance benefits for many scenarios. In the LLVM 3.2 release it wasn't enabled by default, but for LLVM 3.3 it's now enabled when using the -O3 optimization level.

Besides enabling it default for this greatest optimization level, LLVM 3.3 also provided improvements to the loop vectorizer. The LLVM loop vectorizer is now in good standing and so it might be enabled too by default for -O2 and -Os.

There's still some differing views on why the vectorizer should be turned on for -O2, which is the mid optimization level before -O3, but for at least -Os it should be turned on. The -Os level is when optimizing generated binaries for size. The loop vectorizer has the potential of increasing the binary size for some loops, but LLVM is able to weight that information and decide when to vectorize or not.

Apple LLVM developers have now been discussing on the LLVM mailing list about expanding the loop vectorizer's usage by default. The performance wins provided by this vectorizer seem to be worth it to many people even at the potential cost of a slightly longer compile time or the chance that the resulting binary size is slightly larger. This is a change that won't come for LLVM 3.3 but will be for LLVM 3.4 or later; we'll see what happens and post the decision on Phoronix.

LLVM 3.3 also has the interesting SLP vectorizer to optimize straight-line code, but this current discussion is only talking about the loop vectorizer.

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. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. EXT4 In Linux 3.18 Has Clean-ups, Bug Fixes
  2. Emacs 24.4 Has Built-In Web Browser, Improved Multi-Monitor Support
  3. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  4. KDE's KWin On Wayland Begins Using Libinput
  5. Khronos Releases OpenVX 1.0 Specification
  6. Linux Kernel Working Towards GNU11/C11 Compatibility
  7. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  8. Following GCC, Clang Looks To Default To C11
  9. Users/Developers Threatening Fork Of Debian GNU/Linux
  10. Linux 3.18-rc1 Released One Week Early With Many Changes
Latest Forum Discussions
  1. Users/Developers Threatening Fork Of Debian GNU/Linux
  2. Bye bye BSD, Hello Linux: A Sys Admin's Story
  3. HOPE: The Ease Of Python With The Speed Of C++
  4. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  5. AMD Is Restructuring Again, Losing 7% Of Employees
  6. Open-Source AMD Fusion E-350 Support Takes A Dive
  7. Upgrade to Kaveri, very slow VDPAU performance
  8. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems