similar to: April LLVM Austin social is this Thursday!

There are a bunch of us working on LLVM in Austin. So we're organizing a LLVM Austin Social in September. The social will be on Wednesday, September 12 from 5 pm at the BB Rovers Cafe and Pub. It'll be great to meet up with folks in Austin who are also interested in LLVM. Please reply and let me know if you plan on attending so that I can get a count. BB Rovers is on Jollyville road

We probably should not spam the list... but I am in :) Anshu, maybe we can reply directly to you, and at the end you can simply announce the head count? Sergei -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Anshuman Dasgupta > Sent:

Count me in. Some of my colleagues will join as well. Sebastian On Wed, Apr 3, 2019 at 8:44 AM Francesco Petrogalli via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Nice idea Brian, I am based in Austin and I would like to socialize with other LLVM engineers in the area. > > Constrains: I might not be in town for the week of Apr 29 - May 3rd :) > > Francesco > >

Some of my LLVM colleagues that I only seem to encounter at the annual Bay Area dev meeting live right here in Austin, TX. We should get together for a social, yeah? And I suppose there's bound to be more around here who might be interested who haven't been able to trek to San Jose. So consider this an official solicitation to Austin area LLVM fans. Write back with interest and I'l

> On Jun 24, 2019, at 10:53 AM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > > To me, it is also an issue related to SIMD signature matching when the vectorizer kicks in. Losing info from FE to BE is not good in general. > Yes, we cannot loose such information. In particular, the three examples I reported are all generating i64 in the scalar function signature: // Type 1

For example, Type 2 case, scalar-foo used call by value while vector-foo used call by ref. The question Johannes is asking is whether we can decipher that after the fact, only by looking at the two function signatures, or need some more info (what kind, what's minimal)? I think we need to list up cases of interest, and for each vector ABI of interest, we need to work on the requirements and

On 12 December 2016 at 16:49, Francesco Petrogalli <Francesco.Petrogalli at arm.com> wrote: > I am not sure I understand here. In my patch, all I am doing is “vector > symbol awareness generation”. There are no globals that are generated in > the final object file, it is just the TargetLibraryInfoImpl that is being > populated with the info needed by the vectorizer. The

Hi, is there a R function that order a matrix according to some criteria based on the rows(or cols) of that matrix? For example, let's say that my matrix S is composed by n rows S_1, S_2,.., S_n and that I compute some real value g_i=g(S_i) for each row. Then I want to order this set of g_i (from smaller to bigger) and order the correspondent row to the new position. Is it possible (apart

Hi gang. So I'm actually carrying through on the threat I made a couple of months back, and helping to start a local users group for the NYC Metropolitan area. Here's a copy of the announcement of our introductory / planning meeting, I also can send a flyer version of this to anyone who wants (Open Office document, should be viewable in MS-Office). Please feel free to attend,

We'll be at Tied House as usual, starting on Thursday the 5th at 7pm! If you can, help us plan and RSVP here: https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyxgbhb/ See everyone there! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180402/3fa54901/attachment.html>

> What is a `"logically"-widened alwaysinline wrapper for the vector function`? Can you provide an example? Also, what is the `tricky processing` you are referring to that the vectorizer should care about? For the case mentioned earlier: float MyAdd(float* a, int b) { return *a + b; } __declspec(vector_variant(implements(MyAdd(float *a, int b)),

Hello, I am trying to access https://git.llvm.org/git/llvm to be able to cherry pick some of the recent commits I did in the monorepo into our downstream llvm-only repository. The host seems defunct, is this part of the move to the monorepo? I think I can just get the patch and remove the `llvm` on top of the paths, but that’s not a scalable approach. Francesco

Hi Francesco, > I am crafting the attribute so that it makes it explicit that we are using OpenMP and we are expecting a Vector Function ABI. I just thought that another option would be to force FE to always emit "logically"-widened alwaysinline wrapper for the vector function that does the arguments processing according to ABI inside (we need that info in the FE anyway). That way

On Fri, 31 May 2019 at 17:19, Francesco Petrogalli via llvm-dev <llvm-dev at lists.llvm.org> wrote: > TOPIC 2: metadata vs attribute > > Also, @Renato expressed concern that metadata might be dropped by optimization passes - would using attributes prevent that? I think it would, thanks! > TOPIC 3: "there are no special arguments / flags / status regs that are used /

@Xinmin, Saito: If Clang/the frontend generates the version there is no problem, or is there? The frontend knows about the original source type and it's ABI specific lowering already. @Francesco, we should even consider putting the generating capabilities outside of the OpenMP code generation (in the future). That could allow easier reuse by other frontends. Get Outlook for

>Thank you everybody for their input, and for your patience. This is proving harder than expected! :) Thank you for doing the hard part of the work. Hideki -----Original Message----- From: Francesco Petrogalli [mailto:Francesco.Petrogalli at arm.com] Sent: Monday, June 24, 2019 11:26 AM To: Saito, Hideki <hideki.saito at intel.com> Cc: Doerfert, Johannes <jdoerfert at anl.gov>;

> On Nov 15, 2019, at 1:52 AM, Alex Denisov <1101.debian at gmail.com> wrote: > >> I think I can just get the patch and remove the `llvm` on top of the paths, but that’s not a scalable approach. > > IIRC, the -p option of 'patch' is exactly for doing this. Would that simplify your use-case? > Yes, for a single patch that would work. If there is a way to do

Yes, this is very similar, but only expressed in terms of clang attributes, which may have different spellings for clang, GCC, c++11 etc. I don't think GCC will implement this as pragma. They added simd attribute instead of pragma. Best regards, Alexey Bataev > 31 мая 2019 г., в 14:43, Francesco Petrogalli <Francesco.Petrogalli at arm.com> написал(а): > > > >> On

On 12/12/2016 14:32, "Renato Golin" <renato.golin at linaro.org> wrote: >Clang is already able to mangle NEON vectors of any length >(CXXNameMangler::mangleNeonVectorType), you should use that, as this >is very likely to be compatible with other compilers as well. Hi Renato, The “u”, “v”, “l” mangling of parameters has already been agreed internally at ARM with the gcc

Hello everybody, is there a way to tell Sweave to skip the R code and process only the LaTeX part? I know it sounds a little bit weird, but the R code of my document is complete and _slow_ and I need to add the LaTeX part. Thanks, franZ