Alex Bradbury via llvm-dev
2016-Aug-15 11:17 UTC
[llvm-dev] LLVM Weekly - #137, Aug 15th 2016
LLVM Weekly - #137, Aug 15th 2016 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/137>. Welcome to the one hundred and thirty-seventh 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](http://asbradbury.org). 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 at asbradbury.org>, or @llvmweekly or @asbradbury on Twitter. ## News and articles from around the web A number of talk submission deadlines for LLVM-related events are rapidly approaching. The [deadline for the 2016 LLVM Developers' Meeting](http://lists.llvm.org/pipermail/llvm-dev/2016-August/103621.html) is the 25th of August. Paper submissions for [this year's LLVM in HPC workshop](http://lists.llvm.org/pipermail/llvm-dev/2016-August/103615.html) are due on September 1st. Finally, the extended deadline for talk proposals for the [2016 LLVM Cauldron](http://llvm.org/devmtg/2016-09/) is today. Submit your talks now! ## On the mailing lists * Kirill Bobyrev, who has been working on clang-rename is looking for feedback on [adding a clang-refactor tool](http://lists.llvm.org/pipermail/cfe-dev/2016-August/050276.html) which would act as an umbrella for other refactoring modules. Unsurprisingly, everyone response so far is positive about the idea. * Kate Stone has shared some ideas on ['LLDB evolution'](http://lists.llvm.org/pipermail/lldb-dev/2016-August/010870.html), including evaluating the testing strategy, supporting C++ modules, establishing standards for language integration, and being a good citizen in the LLVM community. One suggested way of improving on the final point is to move to LLVM's code formatting standard. Zachary Turner [suggests evaluating adopting lit for LLDB's testing](http://lists.llvm.org/pipermail/lldb-dev/2016-August/010871.html). Chris Lattner [suggests](http://lists.llvm.org/pipermail/lldb-dev/2016-August/010924.html) bringing the discussion about prefixing member variables to the wider LLVM community. * Jeroen Ooms queries the [state of libcxx compatibility with libstdc++](http://lists.llvm.org/pipermail/cfe-dev/2016-August/050275.html). David Chisnall [clarifies](http://lists.llvm.org/pipermail/cfe-dev/2016-August/050278.html) what can and cannot be mixed in one binary. * The discussion surrounding the tradeoffs pro/con a monolothic Git repository for LLVM has rumbled on. Renato Golin [suggests](http://lists.llvm.org/pipermail/llvm-dev/2016-August/103594.html) effort should be focused on preparing a detailed proposal, which can then be put out to a much wider community via a survey. * Eric Fiselier has posted a proposal on [packaging sanitised versions of libc++ with Clang](http://lists.llvm.org/pipermail/cfe-dev/2016-August/050343.html) in order to make MSan and other sanitisers easier to use. ## LLVM commits * Integration of coroutine support continues. Part 6 adds support for elision of dynamic allocation of a coroutine frame and 6b adds a coro.id intrinsic. [r278242](http://reviews.llvm.org/rL278242), [r278481](http://reviews.llvm.org/rL278481). * The ARM backend supports two new relocation models, read-only position independence (ROPI) and read-write position independence (RWPI). In ROPI, code and read-only data sections are accessed PC-relative. In RWPI, read-write data is accessed relative to r9. These can be used individually or together and are designed to avoid the need for a dynamic linker on small systems. [r278015](http://reviews.llvm.org/rL278015). * The new GlobalISel gained support for simple function calls on AArch64. [r278293](http://reviews.llvm.org/rL278293). * A new "resolution-based" link-time optimisation API has been introduced. This is designed for use by ThinLTO. [r278330](http://reviews.llvm.org/rL278330). ## Clang commits * Clang gained support for C++1z decomposition declarations. [r278642](http://reviews.llvm.org/rL278642). * The Clang include-fixer now properly supports processing multiple files in one invocation. [r278102](http://reviews.llvm.org/rL278102). ## Other project commits * The in-tree version of Google Benchmark has been updated to include a `compare_bench.py` script, which was written to make it easy to compare two benchmark runs (and was written for the libcxx use-case). [r278147](http://reviews.llvm.org/rL278147). * As part of EfficiencySanitizer, compiler-rt gained a generic resizing hash table implementation. [r278024](http://reviews.llvm.org/rL278024). * You can now build both shared and static versions of libc++ in a single build. [r278068](http://reviews.llvm.org/rL278068). * std::any was added to libcxx. [r278310](http://reviews.llvm.org/rL278310).
> * The ARM backend supports two new relocation models, read-only position > independence (ROPI) and read-write position independence (RWPI). In > ROPI, code > and read-only data sections are accessed PC-relative. In RWPI, > read-write data > is accessed relative to r9. These can be used individually or together > and are > designed to avoid the need for a dynamic linker on small systems. > [r278015](http://reviews.llvm.org/rL278015). > >This is awesome! Thanks, Oliver, for pushing this through. Those of us building embedded systems in Rust have been hoping for this to make it into LLVM. -Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160903/e0bf2018/attachment.html>