[llvm-dev] LLVM Weekly - #279, May 6th 2019
Bekket McClane via llvm-dev
llvm-dev at lists.llvm.org
Mon May 6 17:52:38 PDT 2019
There seems to be a typo in the mailing list section
> On May 6, 2019, at 11:17 AM, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> LLVM Weekly - #279, May 6th 2019
> If you prefer, you can read a HTML version of this email at
> Welcome to the two hundred and seventy-ninth 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.
> ## News and articles from around the web
> The next Austin LLVM Social will be [on Thursday 30th
> A Toronto LLVM/Clang meetup will take place [on Tuesday 14th
> Jan Hubička has yet another excellent blog post on compiler optimisation, this
> time on [GCC 9's link-time and inter-procedural optimisation
> GCC 9.1 [has been released](https://lwn.net/Articles/787385/).
> Krister Walfridsson blogged on [how LLVM optimises geometric
> ## On the mailing lists
> * Jesper Antonsson shared an
> [RFC](http://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html) on
> removing the assumption that 1 byte == 8 bits. This generated plenty of
> * Graham Hunter [made an
> update](http://lists.llvm.org/pipermail/llvm-dev/2019-April/132054.html) on
> scalable vector types and SVE upstreaming, including a handy diagram showing
> the dependencies of the different components and expected controversy level.
> * Stephen Kelly [shared EuroLLVM roundtable
> notes](http://lists.llvm.org/pipermail/cfe-dev/2019-May/062217.html) on future
> refactoring with AST-matchers.
> * Todd Snider wrote an
> [RFC](http://lists.llvm.org/pipermail/llvm-dev/2019-April/132041.html) on
> supporting additional symbol metadata in ELF object files as supported by some
> ARM compilers. e.g. `int a __attribute__((location(0x1000))) = 4;`.
> * Andrew Kaylor shares an
> [RFC](http://lists.llvm.org/pipermail/llvm-dev/2019-April/132056.html) on
> extending optimisation reporting. He splits this into two categories, 1) ways
> to support different sorts of output, and 2) ways to create connections
> between different events represented in the report.
> * Serge Guelton is seeking feedback on his effort to [generalise LLVM
> extensions that provide new
> allowing projects in tools/ that register themselves with an appropriate CMake
> variable having their passes register in clang/opt/bugpoint.
> * Johannes Doerfert is [seeking
> input](http://lists.llvm.org/pipermail/llvm-dev/2019-May/132082.html) on his
> proposal for the interplan of Clang and Flag and LLVM for OpenMP.
Maybe it’s Clang and Flang?
> * Stephen Scalpone started a thread on [renaming
> suggesting 'fortran' as the name. Most respondents prefer using the 'flang'
> ## LLVM commits
> * The GlobalISel legalizer documentation was updated.
> * More gfx1010 support has been landing in the AMDGPU backend.
> [r359698](https://reviews.llvm.org/rL359698), and more.
> * In preparation for the AArch64 ILP32 support, DAG pointer size can be
> different from the memory representation.
> * FileCheck gained @LINE numeric expressions.
> * The in-tree gn build system gained support for building libunwind, libcxxabi
> and libc++. [r359804](https://reviews.llvm.org/rL359804),
> * RegAllocFast gained a new heuristic to detect values not live-out of a
> block. [r359906](https://reviews.llvm.org/rL359906).
> ## Clang commits
> * Support for the C++2a explicit bool specifier was added.
> * Support for C++2a "familiar template syntax for generic lambdas" was
> committed. [r359967](https://reviews.llvm.org/rL359967).
> ## Other project commits
> * compiler-rt gained a simple crtbegin.o and crtend.o implementation.
> * The LLVM OpenMP library gained OpenMP 5.0 monotonic support.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev