LLVM Weekly - #315, Jan 13th 2020
If you prefer, you can read a HTML version of this email at
Welcome to the three hundred and fifteenth 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 <[hidden email]>, or
@llvmweekly or @asbradbury on Twitter.
## News and articles from around the web
LLVM 10.0.0 [is
on Wednesday 15th January, with a target date of Feb 26th for the final tag.
## On the mailing lists
* Further discussion took place on flang landing in the monorepo, which was
[summarised by Richard
who listed the concerns raised etc.
* Bill Wendling kicked of a discussion on [moving to GitHub pull
This generated a range of responses discussing teh relative merits of
Phabricator's code review vs GitHub, e.g. [this one from David
* Florian Hahn has now posted two patches demonstrating what matrix support in
Clang might look like and [is seeking
* Zakk is seeking input on [how to encode the target-abi into LLVM bitcode for
question is motivated by the RISC-V backend's needs, and Zakk has posted
patches for two possible approaches.
* Volodymyr Sapsai proposed [adding a publish-subscribe mechanism for GitHub
allow people to implement webhooks for LLVM activity without requiring repo
* Serge Pavlov started a discussion on [calling functions from the non-default
querying whether the floating point state should be saved/restored or not.
* JF Bastien has
the thread he started on the proposed LLVM security group and process.
* Jie Zhou started a thread seeking advice on [the best way of implementing
fat pointers for
Chisnall fed back [guidance on what CHERI
* Chris Kenelly started a discussion on [implementing memcpy, memset, memcmp,
and bcmp in LLVM's
email contains a wealth of information on measured distrubtions and thoughts
on trade-offs. "We see hardware support for these operations as the future".
## LLVM commits
* An initial backend stub was committed for the NEC SX-Aurora TSUBASA Vector
* A scheduling model was committed for the AMD Znver2 (Rome) cores.
* check-llvm now runs 50% faster on macOS and 18% faster on Windows thanks to
using an unbounded regex cache.
* The AArch64 backend gained definitions for missing Apple CPU names.
* The MachineIR infrastructure was enhanced with support for target-specific
MIR formatting and parsing. [be841f8](https://reviews.llvm.org/rGbe841f89d00).
* AArch64 and X86 gained support for a new patchable-function-entry attribute
to add NOPs at function entry.
* The developer policy was updated to reflect that now LLVM has moved to Git,
the "Author" commit metadata should be used to reflect the original author,
rather than needing to add a "Patch by J. Bloggs" line to the commit messages.
## Clang commits
* C++ concepts work continues with initial support for function trailing
requires clauses. [b65b1f3](https://reviews.llvm.org/rGb65b1f322bd).
* New `__builtin_align_up`, `__builtin_align_down`, and `__builtin_is_aligned`
builtins were added, working on both pointers and integers. These were
originally implemented in the downstream CHERI fork of LLVM, motivated by a
desire to avoid ptr-to-int casts.
* A new "optionally" AST matcher was added.
* clang-tidy gained a new bugprone-signed-char-misuse check.
## Other project commits
* The vim-lldb plugin was removed from the monorepo as it was unmaintained and
doesn't work with Python 3. [c5adcdc](https://reviews.llvm.org/rGc5adcdc5c88).
* Tests in LLVM's libc project were moved to a top-level test directory.
* New benchmarks were added to libcxx/benchmarks/string.bench.
* LLDB's build page now describes optional dependencies.
LLVM Developers mailing list
|Free forum by Nabble||Edit this page|