LLVM Weekly - #64, Mar 23rd 2015

Welcome to the sixty-fourth issue of LLVM Weekly, a weekly newsletter
(published every Monday) covering developments in LLVM, Clang, and related
projects. LLVM Weekly is brought to you by Alex
Bradbury. Subscribe to future issues at
http://llvmweekly.org and pass it on to anyone else you think may be
interested. Please send any tips or feedback to asb@asbradbury.org, or @llvmweekly or @asbradbury on Twitter.

News and articles from around the web

Students have until Friday 27th March to get their applications in for Google
Summer of Code. This gives the opportunity to get paid $5500 to work on open
source over the summer, under the mentorship of someone from the community.
See
here
for the list of mentoring organisations advertising LLVM-related projects.
Please do help spread the word. I am biased, but I'd like to draw particular
attention to the wide variety of lowRISC GSoC
ideas, including a project to
implement an LLVM pass using tagged memory to provide protection against
control-flow hijacking.

GCC 5 is starting to get near to
release. The first release
candidate is expected in the first week of April.

On the mailing lists

Peter Collingbourne has kicked off a thread on controlling the LTO
optimization
level. Using
LTO can cause a massive increase in compile-time. Peter argues that for some
features, like the recently added control flow integrity checks in Clang, you
require LTO for whole program visibility but perhaps would rather do much
fewer optimisations in order to get a more reasonable compile time. He
proposes a -flto-level command line option.