similar to: EuroLLVM: Women in Compilers and Tools Reception Tickets

Hey Anastasia, all, There's a long-standing CMake issue with the Debian packaging for Clang (LLVM works), described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=862328 I've done some debugging and have a good idea of what should be done, I just don't know enough about Debian packaging details and testing to make much progress. I'd love to hack on this with

Since less than a week is left to EuroLLVM, I would like to remind you about the Hacker Lab! You can find the time and location on the website: https://2018eurollvm.sched.com/ Note, we are still accepting the topics and the current list is as follows: - Improve support for outside of tree users. LLVM and Clang both have a lot of users that don't contribute to the main repository. They are

+ llvm-dev From: Sumner, Brian Sent: Tuesday, May 10, 2016 3:11 PM To: Anastasia Stulova <Anastasia.Stulova at arm.com>; Liu, Yaxun (Sam) <Yaxun.Liu at amd.com>; cfe-dev (cfe-dev at lists.llvm.org) <cfe-dev at lists.llvm.org>; Pan, Xiuli <xiuli.pan at intel.com>; Bader, Alexey (alexey.bader at intel.com) <alexey.bader at intel.com> Cc: Stellard, Thomas

Thanks, Marco! If there is enough interest in this topic we can also organize a separate round table for this discussion. Cheers, Anastasia ________________________________ From: Marco Antognini <Marco.Antognini at arm.com> Sent: 18 October 2019 14:42 To: Anastasia Stulova <Anastasia.Stulova at arm.com>; Simone Atzeni via llvm-dev <llvm-dev at lists.llvm.org>; clang developer

Thanks for your feedback Philip. Could you perhaps explain what the downsides to LLVM are of accepting this as a subproject as I can't really see any myself. Neil ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> Sent: 06 March 2018 23:07:54 To: Anastasia Stulova; Chris

Hello, We have booked a couple of slots during EuroLLVM this year that we would like to dedicate to real hacking!!! Therefore, we would like to offer to the attendees this year an opportunity to escape from the presentation sessions and dive into fun coding to learn something new or to solve some interesting problems. The current proposal is to have 2 x 45 mins on Monday afternoon and 2 x 45

On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >> SPIR-V does not have to be a part of LLVM for you to do this. You can add >> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >> that uses the external tool to translate LLVM IR to SPIR-V. > > > Ok. I guess if Clang community accepts this way, it would be better to set up

Hi Chris, The main benefit for LLVM to include SPIRV support directly is to increase the number of users and developers in the area of heterogeneous computing, e.g. GPUs, FPGAs, DSPs. We want to increase the number of such devices that LLVM natively supports by adding compilation to SPIRV due to the shortage of proprietary backends in upstream LLVM. Just to clarify we are currently suggesting

LLVM Weekly - #220, Mar 19th 2018 ================================= If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/220>. Welcome to the two hundred and twentieth 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 27 Feb 2018, at 9:07 pm, Anastasia Stulova via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: > SPIR-V does not have to be a part of LLVM for you to do this. You can add > the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) > that uses the external tool to translate LLVM IR to SPIR-V. Ok. I guess

> SPIR-V does not have to be a part of LLVM for you to do this. You can add > the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) > that uses the external tool to translate LLVM IR to SPIR-V. Ok. I guess if Clang community accepts this way, it would be better to set up the SPIRV converter as a tool of LLVM. So the question is are there any

I don't see any problem mangling it to be honest even though there seems to be only one prototype anyways. We could add restrict in as well. Cheers, Anastasia ________________________________ From: Hongbin Zheng <etherzhhb at gmail.com> Sent: 17 September 2016 05:32:54 To: Liu, Yaxun (Sam) Cc: cfe-dev at lists.llvm.org; llvm-dev; Bader, Alexey (alexey.bader at intel.com); Anastasia

On 02/26/2018 09:25 AM, Anastasia Stulova wrote: > >> This is great to see. Is this code the basis of the forks that Anastasia > talked about or did those come from somewhere else? > > > Yes, indeed the base is https://github.com/KhronosGroup/SPIRV-LLVM/ and then there are multiple forks that include some rework as well (some of which were announced on the LLVM channels).

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

On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have to be a part of LLVM for you to do this. You can add >>> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >>> that uses the external tool to translate

Dear all, I would like announce a round table planned for the upcoming LLVM Dev meeting next week that will cover various topics related to the use of LLVM in the compiler stacks for the GPUs. Here is the initial list of discussion topics: - Canonicalization vs. GPUs: Type mutation; - Control flow mutation (graphics shaders are more sensitive to this); - Divergence/reconvergence sensitivity;

Registration is now open for the 2018 European LLVM Developers’ Meeting <http://llvm.org/devmtg/2018-04/> in Bristol, UK. You may register here: https://www.eventbrite.com/e/2018-european-llvm-developers-meeting-bristol-tickets-42283244322 <https://www.eventbrite.com/e/2018-european-llvm-developers-meeting-bristol-tickets-42283244322> Registration fees are $300 for the 2-day event

Hi Simon, The page will be updated later today with the new rate. Kind regards, Arnaud On Tue, Feb 26, 2019 at 12:52 PM Simon Dardis via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > The EventBrite page is showing sales have ended, will it be reopening with > the higher rate soon? > > Thanks, > Simon > > On Tue, 26 Feb 2019 at 00:20, Tanya Lattner via

On Mon, 10 Sep 2018 at 18:47, Nicholas Wilson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I was going to wait until Neil Trevett got back to me about becoming a > SPIR-V TSG advisor but this seems like just as good an opportunity. Please > see the previous discussion [1] if you have not already, there were many > relevant points made. > > First, I’d like to note