Earlier this week when writing about the state of the Tiny C Compiler, I learned more about QCC. QCC is a new initiative to pair a forked version of the Tiny C Compiler (TCC) with QEMU's code generator.
Aside from why LLVM/Clang was ported to one of the fastest super computer's in the world and using Clang to implement Microsoft's C++ AMP, another interesting session at this month's LLVM Developers' Conference in San Jose was about using Clang to analyze code comments.
Most often whenever writing about LLVM and its Clang C/C++ compiler front-end on Phoronix, within the forums is a flurry of comments from those in support of and against this modular compiler infrastructure. Some are against LLVM/Clang simply because its BSD-licensed and sponsored by Apple rather than the GPLv3-licensed GCC backed by the FSF. Others, meanwhile, see LLVM as presenting unique advantages and benefits. What reasons would a leading US national laboratory have for deploying LLVM/Clang to their leading super-computer? Here's an explanation from them.
Microsoft conceived C++ Accelerated Massive Parallelism (AMP) as a library atop DirectX 11 for offering data-parallelism directly in C++ that can make easy use of GPUs while having CPU fall-back support. With C++ AMP being similar to OpenCL, Intel engineers decided to implement the Microsoft specification within OpenCL and using LLVM/Clang so that it can be used cross-platform.
While the Tiny C Compiler may be quick at compiling code, the lightweight C compiler hasn't been too quick to advance with new releases and features.
The first release candidate of the LLVM 3.2 compiler infrastructure along with the Clang C/C++ front-end compiler is now available.
The GCC 4.8 compiler when released in early 2013 will have a number of new optimizations.
At Chris Lattner's keynote for the LLVM Developers' Conference that took place last week in California, he called for more "code owners" within the LLVM code-base.
The components making up LLVM 3.2 were all branched last night in preparation for an official release in December.
After talking about FreeBSD's transition to Clang as the default C/C++ compiler rather than GCC, the move has finally happened where for x86/x86_64 systems the LLVM-based compiler has replaced GCC.
GCC 4.8 has reached the end of new development activity.
GCC developers have brought up the topic of tagging a GCC 5.0 release soon based upon recent changes.
While it hasn't been a news item for a couple months, a group of developers are still hard at work to advance the LLVM/Clang compiler and the Linux kernel to a point where this alternative compiler to GCC can be used for building the Linux kernel.
ESL, the Embedded Systems Language, is a new programming language intended for embedded/small systems and its compiler was implemented atop the LLVM infrastructure.
The GCC trunk is nearing the completion of stage one development for the GCC 4.8 release due out in early 2013.
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.
The first development release of the GNOME 3.8 is now available with new features for the GNOME desktop.
A loop vectorizer has been committed to LLVM 3.2 that's capable of automatically vectorizing small loops.
The ARM 64-bit compiler port (AArch64) of the GNU Compiler Collection is now ready for merging to trunk.
The LRA branch has been merged into GCC trunk as a new feature of GCC 4.8.
Developers at a university in China have developed their own Java version of LLVM. Their reasoning for re-implementing LLVM is that they prefer Java to the C++ language.
Developers from ARM Holdings have published their initial ARMv8 patch for the GNU Compiler Collection for the 32-bit "AArch32" compiler port.
Aside from greater C++11 compliance and early C++1y support, GCC 4.8 as the next major Free Software Foundation compiler release will also have many other interesting features.
The LLVM project has announced that they will be turning to Facebook's "Phabricator" project for handling code review.
GCC 4.8 is set to support more of the C++11 ISO standard and it also starts working on very early support for "C++1y", the next C++ standard that is still years away.
The Linux 3.7 kernel introduces support for 64-bit ARM, a.k.a. AArch64. In further enabling 64-bit ARM support under Linux, the GCC Steering Committee has now officially accepted the AArch64 port of the GNU Compiler Collection. 64-bit ARM now has a compiler!
Developers behind GUPC, the GNU Unified Parallel C implementation, are still hoping to see their several year old project merged into the GCC 4.8 compiler release.
There's patches available for those wishing to try out experimental OpenMP support for the LLVM/Clang C/C++ compiler.
GCC developers continue to work on bringing AddressSanitizer, which is part of the LLVM project, to their open-source compiler in hopes of better catching memory bugs and errors.
Polly was accepted at the beginning of this year as an official LLVM project and since then it's continued to advance ahead of the LLVM 3.2 release for providing polyhedral optimizations.
612 Compiler news articles published on Phoronix.