similar to: LLVM Weekly - #215, Feb 12th 2018

I was going to say, this reminds me of Kai's presentation at Fosdem yesterday. https://fosdem.org/2018/schedule/event/heterogenousd/ It's always good to see the cross-architecture power of LLVM being used in creative ways! :) cheers, --renato On 5 February 2018 at 13:35, Nicholas Wilson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Interesting. > > I do something

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

Interesting. I do something similar for D targeting CUDA (via NVPTX) and OpenCL (via my forward proved fork of Khronos’ SPIRV-LLVM)[1], except all the code generation is done at compile time. The runtime is aided by compile time reflection so that calling kernels is done by symbol. What kind of performance difference do you see running code that was not developed with GPU in mind (e.g.

HI LLVM comunity, after 3 years of development, various talks on LLVM-HPC and EuroLLVM and other scientific conferences I want to present my PhD research topic to the lists. The main goal for my research was to develop a single-source programming model equal to CUDA or SYCL for accelerators supported by LLVM (e.g., Nvidia GPUs). PACXX uses Clang as front-end for code generation and comes with

LLVM is participating in the Outreachy May 2018 to August 2018 internships. We are seeking mentors to propose projects that Outreachy interns can work on during their internship. For our first time with this program, the LLVM Foundation will be sponsoring 1 intern. Ideally we would like a few project proposals for applicants to pick from. These can range from entry level documentation projects to

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 - #216, Feb 19th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/216>. Welcome to the two hundred and sixteenth 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 - #214, Feb 5th 2018 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/214>. Welcome to the two hundred and fourteenth 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 Mon, Mar 19, 2018 at 10:35:30AM +0530, Arushi Singhal wrote: > This patch replace list_entry with list_{next/prev}_entry as it makes > the code more clear to read. > Done using coccinelle: > > @@ > expression e1; > identifier e3; > type t; > @@ > ( > - list_entry(e1->e3.next,t,e3) > + list_next_entry(e1,e3) > | > - list_entry(e1->e3.prev,t,e3)

On Mon, 19 Mar 2018, Arushi Singhal wrote: > This patch replace list_entry with list_{next/prev}_entry as it makes > the code more clear to read. > Done using coccinelle: > > @@ > expression e1; > identifier e3; > type t; > @@ > ( > - list_entry(e1->e3.next,t,e3) > + list_next_entry(e1,e3) > | > - list_entry(e1->e3.prev,t,e3) > +

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

On Tue, Mar 20, 2018 at 11:29:27AM -0700, Santha Meena Ramamoorthy wrote: > Replace drm_gem_object_reference/unreference function with *_get/put() > suffixes, because it is shorter and consistent with the kernel > kref_get/put() functions. The following Coccinelle script was used: > > @@ > expression e; > @@ > > ( > -drm_gem_object_reference(e); >

On Mon, Mar 19, 2018 at 12:44 PM, Julia Lawall <julia.lawall at lip6.fr> wrote: > > > On Mon, 19 Mar 2018, Arushi Singhal wrote: > > > This patch replace list_entry with list_{next/prev}_entry as it makes > > the code more clear to read. > > Done using coccinelle: > > > > @@ > > expression e1; > > identifier e3; > > type t; >

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

TL;DR This RFC is a joint effort by Intel and Saarland University to bring the divergence analysis of the Region Vectorizer [1,2,3,4,5] (dubbed the vectorization analysis of RV) to LLVM. The implementation is available on github for feedback [0]. The existing divergence analysis infrastructure in LLVM has conceptual limitations (structured control, SCEV based). The new analysis resolves bugs

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

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

On 8 May 2018 at 16:34, James Courtier-Dutton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Has something changed? > So, it seams that LLVM do not participate in Outreachy. Last email from Tanya was looking for folks to participate, there was no update that it wouldn't happen. Maybe this is a new development? Anyway, I think if the foundation considers this again, there

Hello guys! I'm Shraddha , an opensource enthusiast and a regular contributor to the linux-kernel project. I'm currently an intern at Linux Kernel selected through the Outreachy program. I started contributing to opensource only 5 months ago but I'm already quite active. I would like to join the centos project.Any help on getting started is appreciated :) Kind Regards, Shraddha --