[llvm-dev] LLVM Weekly - #204, Nov 27th 2017

Alex Bradbury via llvm-dev llvm-dev at lists.llvm.org
Mon Nov 27 14:36:23 PST 2017


LLVM Weekly - #204, Nov 27th 2017
=================================

If you prefer, you can read a HTML version of this email at
<http://llvmweekly.org/issue/204>.

Welcome to the two hundred and 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](https://www.linkedin.com/in/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 at asbradbury.org>, or
@llvmweekly or @asbradbury on Twitter.

I'm in the Bay Area this week for the [7th RISC-V
Workshop](https://riscv.org/2017/10/7th-risc-v-workshop-agenda/), where I'll
be presenting about the RISC-V LLVM backend work that we have been
spearheading at lowRISC CIC. I hope to see some of you there.


## News and articles from around the web

The submission deadline for the LLVM toolchain devroom at FOSDEM 2018 [has
been
extended](http://lists.llvm.org/pipermail/llvm-dev/2017-November/119289.html)
to Sunday 3rd December.

The next LLVM Social Berlin will take place [on Thursday 30th
November](http://lists.llvm.org/pipermail/llvm-dev/2017-November/119264.html).
It features a talk "Auto-tuning Compiler Transformations with Machine
Learning" by Dr. Biagio Cosenza.

A RISC-V Rust toolchain is [now
available](https://github.com/dvc94ch/riscv-rust-toolchain), courtesy of David
Craven. This builds on top of the ongoing [RISC-V LLVM backend
work](https://github.com/lowrisc/riscv-llvm).


## On the mailing lists

* Jonas Paulsson is [looking for
feedback](http://lists.llvm.org/pipermail/llvm-dev/2017-November/119250.html)
on introducing new scheduling heuristics.

* Ben Hamilton proposes [having cfe-commits automatically CCed on Clang patch
reviews](http://lists.llvm.org/pipermail/cfe-dev/2017-November/056032.html).
This has now [been
enabled](http://lists.llvm.org/pipermail/cfe-dev/2017-November/056107.html)
for reviews submitted against the Clang repository.

* Hewlett Packard Enterprise have
[shared](http://lists.llvm.org/pipermail/llvm-dev/2017-November/119232.html)
that SPEC CPU 2017 scores for an AMD EPYC processor targeted by the LLVM-based
[AOCC](http://developer.amd.com/amd-aocc/) compiler are now available
([integer](https://spec.org/cpu2017/results/res2017q4/cpu2017-20171031-00334.html),
[floating
point](https://spec.org/cpu2017/results/res2017q4/cpu2017-20171031-00366.html)).


## LLVM commits

* Initial support was added for Intel's Control-Flow Enforcement Technology.
[r318996](http://reviews.llvm.org/rL318996).

* VPlan gained support for modeling masking.
[r318645](http://reviews.llvm.org/rL318645).

* Further RISC-V codegen patches have landed.
[r318735](http://reviews.llvm.org/rL318735),
[r318737](http://reviews.llvm.org/rL318737).

* MC layer support was added for a number of Intel Icelake instructions.
[r318740](http://reviews.llvm.org/rL318740),
[r318745](http://reviews.llvm.org/rL318745),
[r318746](http://reviews.llvm.org/rL318746), and more.


## Clang commits

* The NetBSD Clang driver can now be used to enable ESan, KASan, MSan, and
Scudo. [r319007](http://reviews.llvm.org/rL319007).

* The `clang-tidy/rename_check.py` helper script gained support for moving
checks between modules, and this support was used to move a number of checks
from 'misc' to 'bugprone'. [r318905](http://reviews.llvm.org/rL318905).


## Other project commits

* The libcxxabi demangler now supports the `abi_tag` attribute.
[r318874](http://reviews.llvm.org/rL318874).

* The LLDB code for parsing an ELF core file was refactored into smaller
functions. [r318903](http://reviews.llvm.org/rL318903).


## Review corner

The LLVM Weekly review corner serves to highlight patches that are stuck
waiting awaiting review, or work from first-time contributors. See
[here](http://llvmweekly.org/reviewcorner) for more information and how to
submit you work for inclusion. Of course the hope is that highlighting these
patches will enable LLVM Weekly readers will step up and help to get them
merged. I'll be reporting back each week on any activity generated on these
patches, as well as sharing a new batch. If you want your patch included you
must submit it via the linked form.

There were no new patch submissions this week.


More information about the llvm-dev mailing list