similar to: LLVM Weekly - #209, Jan 1st 2018

LLVM Weekly - #211, Jan 15th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/211>. Welcome to the two hundred and eleventh 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 - #212, Jan 22nd 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/212>. Welcome to the two hundred and twelfth 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 - #210, Jan 8th 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/210>. Welcome to the two hundred and tenth 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

After LLVM Weekly was removed from the LLVM blog, it's no longer accessible from LLVM.org. Shouldn't it be linked somewhere? For example, in the Useful Links section, right above the mailing list links. Or in the Site Map section, above the Blog link. On Mon, Jan 30, 2017 at 10:12 AM, Alex Bradbury via llvm-dev < llvm-dev at lists.llvm.org> wrote: > LLVM Weekly - #161, Jan 30th

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

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

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

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

LLVM Weekly - #130, Jun 27th 2016 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/130>. Welcome to the one hundred and thirtieth 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 - #194, Sep 18th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/194>. Welcome to the one hundred and ninety-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

LLVM Weekly - #195, Sep 25th 2017 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/195>. Welcome to the one hundred and ninety-fifth 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 - #222, Apr 2nd 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/222>. Welcome to the two hundred and twenty-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

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

LLVM Weekly - #217, Feb 26th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/217>. Welcome to the two hundred and seventeenth 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 - #218, Mar 5th 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/218>. Welcome to the two hundred and eighteenth 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

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

> 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