search for: anastasia

+ 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, Th...

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 list <cfe-dev at lists.llvm.org> Cc:...

...is way, it would be better to set up the SPIRV converter as a tool of LLVM. So the question is are there any downsides of this? Or would anyone object if we add the converter to the LLVM project as an optional tool? We would of course take care of configuring and maintaining it ourselves. Cheers, Anastasia ________________________________ From: Tom Stellard <tstellar at redhat.com> Sent: 26 February 2018 17:37 To: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org Cc: nd Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On 02/26/2018 09:25 AM, Anastasia Stulova 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 LLVM IR to SPIR-V. > > > Ok. I guess...

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 LLVM IR to SPIR-V. >> >&gt...

...convergence sensitivity; - Address-space awareness; The round table is preliminary planned for Tue 3-4pm or Wed 2-3pm. The exact slot will be listed in the online schedule soon: https://llvmdevmtg2019.sched.com/ Feel free to let us know of any other topics you would like to cover. Kind regards, Anastasia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191018/64ea2636/attachment.html>

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 Stulova Subject: Re: builtins name mangling in SPIR 2.0 On Fri,...

...e mentioned, the latest OpenCL standards evolve towards off-line compilation from OpenCL C++ to SPIRV. So having SPIRV generation directly in LLVM would allow us to deliver fully complete and compliant OpenCL C++ support, without using any external tools. See discussion with Tom earlier. Thanks! Anastasia ________________________________ From: Chris Lattner <clattner at nondot.org> Sent: 01 March 2018 01:52 To: tstellar at redhat.com Cc: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org; nd Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On Feb 27, 2018, at 10:25 AM, Tom St...

...ownsides 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 Lattner Cc: llvm-dev at lists.llvm.org; nd; Tomeu Vizoso Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool I've only been skimming the discussion thread so far, but so far, I see no strong reason for this to be a LLVM subproject in it's current form. I would recommend...

> 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). I think the biggest problems we are trying to solve is: 1...

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

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

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

...tends that already generate SPIR-V. A more detailed explanation of the complete design proposal is given in this Wiki page: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/wiki/SPIRV-Toolchain-for-Clang Looking forward to any feedback about the proposal or possible collaborations, Thanks! Anastasia

...or example analysis of code coverage by the tests or compilation time hotspots. - Address some bugs that otherwise don't get bandwidth allocated to them. If you like any idea above please vote for it! Do you have any other interesting idea to hack? We would like to hear about it! Cheers, Anastasia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180316/61dc6df7/attachment.html>

+ Alexey Anastasia According to SPIR spec v1.2 s2.10.3 2.10.3 The printf function The printf function is supported, and is mangled according to its prototype as follows: int printf(constant char * restrict fmt, ... ) Note that the ellipsis formal argument (...) is mangled to argument type specifier z It seems prin...

...ated from #random data beta<-matrix(0,1,n.k+1) e<-matrix(0,tslength,n.k+1) for(k in 1:n.k+1) { for(i in 1:tslength) { beta[1,1]<-beta1 e[i,k]<-c(rnorm(1,0,var.all)) beta[1,k]<-summary(lm(e[1:tslength,k]~t))$coefficient[2] } } thanks Anastasia Tzortzaki [[alternative HTML version deleted]]

Hello, I am new to R program, therefore, I am sorry if this is a really stupid question. I wrote a simple function and for some reason it doesn't work ReturnsGrid = function(x,y,m){ for (i in 1:m){ grid[i] <- x + (i-1)*(y-x)/m } grid } xx=ReturnsGrid(0,9,3) Thanks a lot! [[alternative HTML version deleted]]

...luster-users/2018-April/033811.html > I have a same exact setup and below is as far as it went after months of > trail and error. > We all have somewhat same setup and same issue with this - you can find > same post as yours on the daily basis. > > On Wed, Apr 11, 2018 at 3:03 PM, Anastasia Belyaeva < > anastasia.blv at gmail.com> wrote: > >> Hello everybody! >> >> I have 3 gluster servers (*gluster 3.12.6, Centos 7.2*; those are >> actually virtual machines located on 3 separate physical XenServer7.1 >> servers) >> >> They are all...

...onator/llvm-target-spirv/, stripped off of everything > not related to SPIR-V and updated to work with llvm HEAD. > (Some of the commits were lost on the way, so we are in the process of redoing > the stripping and updating.) This is great to see. Is this code the basis of the forks that Anastasia talked about or did those come from somewhere else? -Tom > > One user of that external tool will be Mesa [1] (for its OpenCL implementation > named clover) for > 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by > translating SPIR-V to LLVM IR; (patches un...