similar to: [LLVMdev] LLVM Weekly - #1, Jan 6th 2014

LLVM Weekly - #52, Dec 29th 2014 =============================== If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/52>. Welcome to the fifty-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).

LLVM Weekly - #57, Feb 2nd 2015 =============================== If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/57>. Welcome to the fifty-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).

LLVM Weekly - #46, Nov 17th 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/46>. Welcome to the forty-sixth 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).

LLVM Weekly - #157, Jan 2nd 2017 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/157>. Welcome to the one hundred and fifty-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

LLVM Weekly - #161, Jan 30th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/161>. Welcome to the one hundred and sixty-first 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

LLVM Weekly - #189, Aug 14th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/189>. Welcome to the one hundred and eighty-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

LLVM Weekly - #39, Sep 29th 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/39>. Welcome to the thirty-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](http://asbradbury.org).

LLVM Weekly - #16, Apr 21st 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/16> Welcome to the 16th 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

On 27 August 2017 at 00:01, Alex Bradbury <asb at asbradbury.org> wrote: > Hi all. I'm assuming most people reading this email are familiar with LLVM's > code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> > as well as LLVM Weekly, the development newsletter I've written and sent out > every Monday since Jan 2014. Since that time,

Hi all. I'm assuming most people reading this email are familiar with LLVM's code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> as well as LLVM Weekly, the development newsletter I've written and sent out every Monday since Jan 2014. Since that time, it's provided something of a "signal boost" for important mailing list discussions and

LLVM Weekly - #56, Jan 26th 2015 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/56>. Welcome to the fifty-sixth 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).

Yea, I'll try to get that set up eventually. It'll just take longer to push that change than the little splash. On Sat, Apr 5, 2014 at 10:16 AM, Alex Bradbury <asb at asbradbury.org> wrote: > On 5 April 2014 17:26, Manuel Klimek <klimek at google.com> wrote: > > We (hopefully successfully) migrated our phabricator servers to a new > home. > > As part of

LLVM Weekly - #43, Oct 27th 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/43>. Welcome to the forty-third 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).

On 11 May 2014 13:25, Alex Bradbury <asb at asbradbury.org> wrote: > On 6 May 2014 09:42, Jay Foad <jay.foad at gmail.com> wrote: >> I followed a link from LLVM Weekly to http://reviews.llvm.org/rL207598 and got: >> >> " >> Still Importing... >> >> This commit is still importing. Changes will be visible once the >> import finishes.

LLVM Weekly - #215, Feb 12th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/215>. Welcome to the two 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

Hello, I am writing a compiler which outputs LLVM for my own custom language. Thanks to everybody who has contributed to the project it really is an impressive tool chain. I downloaded the 3.7 release from the website and I noticed that there had been a change to getelementptr. I can see the new syntax in the latest version of the Language Reference Manual but I could find no other reference to

Hello all, I recently felt the need to have debug info at the LLVM IR level (because my frontend's semantics vastly differ from IR that it doesn't make much sense to use it). Asm can sometimes be too "low level", so it's nice to have the ability to single-step at the IR level. The pass that used to do this (-debugir) bitrotted and was removed from tree. I spent the weekend

At least one proprietary linker put a lot of effort into deduplicating and rewriting debug information. This took up the majority of the link time despite serious engineering time on performance optimisation. For example, some sections were written from scratch by the linker because that proved faster than parsing the input. Teaching LLD to dedup DWARF should be expected to dramatically slow it

LLVM Weekly - #82, Jul 27th 2015 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/82> Welcome to the eighty-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).

The 3.6 release is drawing nearer, but the release notes could still use a lot of improvement: LLVM: https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst Clang: https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst The good news is that they can be updated all the way up until release. If you have a patch for the release notes, commit it directly to the