similar to: [LLVMdev] LLVM Weekly - #39, Sep 29th 2014

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 - #113, Feb 29th 2016 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/113>. Welcome to the one 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 - #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

Is it possible to inline functions compiled from C++ code into generated code that is fed, Module by Module, into the ORC JIT? I'd like to add a Module compiled from C++ code into the JIT and then as I add later modules, functions from the first module are inlined in the later ones. I already do this for file compilation/linking in my Common Lisp compiler “Clasp” (github.com/drmeister/clasp

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

I’m developing a Common Lisp compiler for OS X and Linux that uses LLVM as its backend and interoperates with C++. It’s at: github.com/drmeister/clang I need to compile one C++ source file containing small, intrinsic functions into an LLVM-IR bitcode file and link it with bitcode generated by my compiler running LLVM3.6.1. I have been unable to do this for more than a year and I was hoping

Hello everyone, Is fully relocatable/position-independent JITted code on the horizon or currently possible with LLVM? I’ve written a Common Lisp compiler (currently called Clasp: https://github.com/drmeister/clasp) in C++ that uses LLVM as the backend and interoperates with C++. It uses copying garbage collection via the Memory Pool System (MPS) garbage collector by Ravenbrook. This garbage

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

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

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