[llvm-dev] LLVM Weekly - #132, Jul 11th 2016

Alex Bradbury via llvm-dev llvm-dev at lists.llvm.org
Mon Jul 11 09:16:43 PDT 2016

LLVM Weekly - #132, Jul 11th 2016

If you prefer, you can read a HTML version of this email at

Welcome to the one hundred and thirty-second 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.

I'm in Boston this week for the [4th RISC-V
workshop](https://riscv.org/2016/07/4th-risc-v-workshop-final-agenda/). If
you're going to be there, Wei Song, Rob Mullins and myself are all keen to
talk about our [lowRISC](http://www.lowrisc.org) effort to produce an
open-source RISC-V based SoC. Wei will be presenting our most recent update,
adding trace debug support. You might also be interested in the [work our
interns have been up
on adding video output.

## News and articles from around the web

Bruce Mitchener has announced [high-level Rust bindings for the LLDB

The first [LLVM Cauldron](http://llvm.org/devmtg/2016-09/) will take place on
September 8th in Hebden Bridge, UK.
Registration is free. Since last week, we've confirmed more details about the
[keynote on optimising with persistent data structures by Andy
Wingo](http://llvm.org/devmtg/2016-09/#schedule). What are you waiting for?
Register and submit your talks now!

The 2016 US LLVM Developers Meeting was announced last week, and I think it's
worth a reminder. [Register and/or submit a talk

## On the mailing lists

* The discussion on moving LLVM repositories to  Github is still ongoing.
Renato Goling has written [another recap of recent

* "Jay K" has written a very helpful [summary of Windows/x64 exception

* John Criswell started a thread about [whether discussions should be
with recent examples being the code of conduct or the potential move to
Github. Answers discussed both the practical issues raised (such as many would
reply-all but wouldn't be members of all lists, causing more work for
moderators) and whether it would make sense to [set up an llvm-project
list](http://lists.llvm.org/pipermail/llvm-dev/2016-July/102000.html) for
these kind of discussions.

* Dean Michael Berris has shared an RFC on [LLVM changes for nop-sleds to
support XRay function

## LLVM commits

* llvm-cov gained support for creating html reports.

* A `writeonly` attribute was added. As you would expect, this indicates a
function may write to but does not read memory. It can also be applied to an
argument where it means the function won't read through that pointer argument.

* The AArch64 backend now makes use of TableGen for handling system
instruction operands. [r274576](http://reviews.llvm.org/rL274576).

* The Sparc backend now has more workarounds for Leon errata.

## Clang commits

* The clang-rename tool gained basic Vim integration.

* The Clang codebase now uses ArrayRef in more interfaces.

## Other project commits

* LLD added support for ARM and Thumb interworking thunks.

* LLDB gained a data formatter for libstdc++ `shared_ptr` and `weak_ptr`.

More information about the llvm-dev mailing list