similar to: LLVM Weekly - #157, Jan 2nd 2017

I want to second Andrey here and then some. I think it is very easy to lose sight of how valuable the work you're doing with the LLVM weekly summaries is to the community. The new year is a great time to reflect on that and I want to add my voice of support and thanks. I think this kind of newsletter is one of the only ways the community can continue to scale. Please reach out for

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

On 18 May 2016, at 07:45, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi everybody, > > I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog. > > However, I can’t omit bike-shedding :) > > Forgive me my directness, but current blog doesn’t look like something close to 2016. > > The

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).

> On May 18, 2016, at 12:59 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > On 18 May 2016, at 07:45, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi everybody, >> >> I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog. >> >> However, I can’t

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,

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).

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

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 - #1, Jan 6th 2014 ============================== Welcome to the inaugural issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. I've been a long time lurker on the LLVM and Clang mailing lists and have been using LLVM extensively in my PhD research for the past 4 years. I thought it might be worthwhile to

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

Hi everybody, I do write some Clang/LLVM related articles on my blog[1][2], and I will be happy to write for LLVM’s blog. However, I can’t omit bike-shedding :) Forgive me my directness, but current blog doesn’t look like something close to 2016. The blog already has lots of great articles. But it’s so hard to grasp valuable information when you have to read non-highlighted C++ code. I think I

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).

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

Hello! I am looking for a handful of people to help write blog posts for the LLVM blog (blog.llvm.org <http://blog.llvm.org/>) or to help recruit volunteers to write blog posts. The LLVM Project blog is a great place to share details about recent changes to LLVM, Clang, and related sub-projects. It also is a great place to highlight users of LLVM. You can write about your work or the work

Hi all, First of all, I'm sorry to create a separate thread on the mailing list, I have disabled all mails from it. I just read the thread about the bug closing protocol thanks to LLVMWeekly. (http://lists.llvm.org/pipermail/llvm-dev/2018-June/123955.html) I've noticed a lot of reactions from people involved with the solving part of the bugs. So I'm putting out the loggers point of

https://reviews.llvm.org/D41659 Implemented missing trigonometric optimization in llvm. Here we have implemented the following missing trigonometric optimizations. 1. tan(x)*cos(x)=sin(x) 2. sin(x)*cos(x) = sin(2*x)/2 3. sin(x)/tan(x)=cos(x); 4. tan(x)/sin(x)=1/cos(x); -------------- next part -------------- An HTML attachment was scrubbed... URL:

So Reid, you'll be running a BoF on this at the October dev meeting? ☺ --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev Sent: Wednesday, June 20, 2018 6:12 PM To: JVApen at gmail.com Cc: llvm-dev Subject: Re: [llvm-dev] Bug-closing protocol Thanks for taking the time to report bugs! I think you are responsible for filing the most