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

Features Coming For The LLVM 3.4 Compiler Stack

Compiler

Published on 27 October 2013 12:51 AM EDT
Written by Michael Larabel in Compiler
Comment On This Article

Having yesterday covered the features so far of GCC 4.9, here's a look at the features baking for LLVM 3.4 -- the next major compiler infrastructure update due out likely around the end of the year.

Compared to the GNU Compiler Collection seeing just about one major update per year, LLVM sees new releases about every six months. LLVM 3.3 came in June and was a great update, but LLVM 3.4 will bring even more to this increasingly used and relied upon open-source compiler stack and its C/C++ compiler front-end.

Among the items queued up right now in mainline LLVM 3.4 include:

- Expanded use of the Loop Vectorizer. LLVM's Loop Vectorizer was already in use for the -O3 optimization level in LLVM 3.3, but now it's also used at -O2 and -Os optimization levels too.

- AMD's R600 back-end is now enabled by default and is no longer marked as being an experimental LLVM back-end.

- The R600 LLVM back-end now supports MSAA and various other new functionality for the GPU LLVM back-end. There's also Sea Islands Compute Support.

- NEON support for AArch64, the 64-bit ARM architecture back-end support in LLVM.

- The SLP Vectorizer is enabled by default. The LLVM SLP Vectorizer was introduced with 3.3 and optimizes the performance of straight-line code.

- Dropping old Visual Studio support and other old/deprecated LLVM code.

- Some compiler performance changes.

- On a related note, the LLDB debugger now has better remote debugging capabilities.

More LLVM / Clang 3.4 coverage will come as the official release approaches.

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. Even With Re-Clocking, Nouveau Remains Behind NVIDIA's Proprietary Linux Driver
  2. The Power Consumption & Efficiency Of Open-Source GPU Drivers
  3. AMD R600g/RadeonSI Performance On Linux 3.16 With Mesa 10.3-devel
  4. Intel Pentium G3258 On Linux
Latest Linux Articles
  1. Nouveau vs. Radeon vs. Intel Tests On Linux 3.16, Mesa 10.3-devel
  2. KVM Benchmarks On Ubuntu 14.10
  3. X.Org Server 1.16 Officially Released With Terrific Features
  4. Ubuntu With Linux 3.16 Smashes OS X 10.9.4 On The MacBook Air
Latest Linux News
  1. Age Of Wonders III Is Still Being Ported To Linux
  2. Git 2.1 To Further Mainline Windows Support Patches
  3. Debian 8.0 Jessie Is Settling For Linux 3.16
  4. Meson: A Next-Gen Build System Showing Promise
  5. Linux 3.16-rc7 Calms Things Down For The Linux 3.16 Kernel
  6. Open-Source AMD Users Report Hawaii GPU Acceleration Is Working
  7. Linus Torvalds On GCC 4.9: Pure & Utter Crap
  8. Cauldron 2014: GCC & LLVM Will Look To Collaborate More
  9. GCC Receives ACM Programming Languages Software Award
  10. KDE 4.14 Beta 3 Released
Latest Forum Discussions
  1. Porting Mesa to the Playstation 2
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. ASRock AM1H-ITX: One Of The Best AM1 Mini-ITX Motherboards
  4. Debian + radeonsi
  5. Open-source drivers on ATI R7 260X
  6. Table test
  7. How To Setup Radeon DPM On Ubuntu Linux
  8. New build, first Linux PC, what could go wrong? ;)