similar to: [EuroLLVM] Hacker's Lab - Topics and Volunteers needed!

Hi Christian, We put your name down for an exception handling table at the same time & room as the ARM (32/64) table [Renato]. I hope this is OK with you. Thanks! -- Johannes On 03/24, Christian Bruel wrote: > Hello, > > If there is a table on Exception handling, Can I have a slot in the agenda > to discuss a proposal to clarify and adapt the attributes used to handle the

We are happy to announce that the list of accepted sessions is available online [0]. The hacker's lab will be organized similar to the one at the US 2016 meeting [1]. To this end, we rely on you to send us topics via mail: eurollvm17-orga at cs.uni-saarland.de We will then look for knowledgeable volunteers and have a selection process to determine which are most interesting for the

Registered, thx! On 03/13, Renato Golin wrote: > On 13 March 2017 at 13:01, Tobias Grosser <tobias.grosser at inf.ethz.ch> wrote: > > I am happy to merge these things. > > Ok. We'll need a big table. :) -- Johannes Doerfert Researcher / PhD Student Compiler Design Lab (Prof. Hack) Saarland Informatics Campus, Germany Building E1.3, Room 4.31 Tel. +49 (0)681

On Mon, Mar 13, 2017, at 02:00 PM, Renato Golin wrote: > On 13 March 2017 at 12:53, Tobias Grosser <tobias.grosser at inf.ethz.ch> > wrote: > > would be glad to have a table around loop optimization or LLVM in HPC. > > Would you be ok if we merged Polly into it? Or do you think we should > keep them separate, but nearby? I am happy to merge these things. Best, Tobias

All, We need volunteers for the Hacker’s Lab at the upcoming 2017 LLVM Developers’ Meeting! The Hacker’s Lab is for small groups to form to discuss topics or work on problems. Please let me know ASAP if you will able to volunteer so I can add your topic to the online listing and make appropriate signs. The Hackers Lab is split into 1.5 hour sessions. During each session, the Hackers Lab will

On Mon, Mar 13, 2017, at 01:46 PM, Renato Golin via llvm-devmeeting wrote: > On 8 March 2017 at 16:10, Johannes Doerfert via llvm-devmeeting > <llvm-devmeeting at lists.llvm.org> wrote: > > Backends, > > It'd be good to have one table for each (combined) back-end, at least > one for Intel (32/64) and ARM (32/64). > > I volunteer to stay at the ARM table.

On 03/20/2018 05:05 AM, Michael Kruse wrote: > There's none yet according to http://llvm.org/devmtg/2018-04/#talks > > Unfortunately, I won't be present, but IMHO it would be nice to have one. I agree. This seems like a good idea.  -Hal > > Michael > > > > 2018-03-20 7:50 GMT+01:00 Renato Golin <renato.golin at linaro.org>: >> Hey folks, >>

Hello, Is there a analysis pass which calculates the ModRefBehaviours OnlyReadsPointerArguments and OnlyAccessesPointerArguments? I tried to find one but so far I only saw that different AA's return OnlyReadsMemory and DoesNotAccessMemory if the readonly and readnone attributes are set. Best regards and thanks in advance, Johannes -- Johannes Doerfert Researcher / PhD Student

Hi Johannes, Actually, I'm working in the same scenario, i.e. configure + make of a benchmark/program/library like you said. I've got your point of using this script as a replacement to generate .bc files instead of a executable. That's truly helpful and has already answered my original question. Now I'm actually moving a step further. Take the same example in your reply, say, if

@Vivek, thanks for your answer and especially these links! I just want to add two more though I am not sure if they are useful here: - Some slides [0] that explain the general structure of LLVM and LLVM-IR I used in our compiler class last year [0]. - Examples that build LLVM-IR "from scratch". These were designed to help students to build an LLVM-IR frontend for their AST.

Hi Johannes, Sanjoy has given you great information already. On Sun, Apr 10, 2016 at 5:19 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Johannes Doerfert wrote: > > Is there any plan to use e.g., post-dominance information to > > propagate wrapping flags? > > None that I'm aware of. > > > If x +nsw y post-dominates the entry block > >

".... the problem Mehdi pointed out regarding the missed initializations of array elements, did you comment on that one yet?" What is the initializations of array elements question? I don't remember this question. Please refresh my memory. Thanks. I thought Mehdi's question is more about what are attributes needed for these IR-annotation for other LLVM pass to understand and

Hal, Johannes, Thanks for the feedback. I have been digging into this a little bit more and was able to have some of this metadata being generated. Nevertheless, I am confused about the semantics of this metadata. Let me explain: I was expecting the alias metadata to complement the information that alias analysis passes compute. However, it seems that the alias information of the pointers used

Hey, I was just informed that my ScalarEvolution patch failed the lld tests on x86_64-freebsd, however on my machine x86_64-linux all tests (llvm+lld) pass for a debug as well as a release build. Furthermore, I'm a bit confused about the error message just before the segfault happens: "Unable to find lib.exe in PATH" Could somebody help me track down the problem? Thanks in

Hi Johannes, By following your directions, I can use your script as is to produce the .bc file now. Here's my command line for compiling s_sin.c into s_sin.bc file and the output: command line: ~/Downloads/newlib-2.1.0/newlib/libm/mathfp » python ~/llvm_link.py s_sin.c -I../common/ -I../../libc/include/ -o s_sin.bc output: Initiate CLANG (/path-to-clang): Options: 's_sin.c

On 01/11, Daniel Berlin via llvm-dev wrote: > > > > def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], > > [IntrArgMemOnly], > > "llvm.experimental.directive">; > > > > def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], > > [IntrArgMemOnly], > >

Hi! There are a lot of accepted but not closed revisions in Differential. Many of them were actually committed, but without Differential revision link or when it was specified in wrong way. I think will be good idea to create script which will match committed revisions with those in Differential: file list should be same and hashes of changed line could be calculated for each file. In case of

<mehdi.amini at apple.com>, Bcc: Subject: Re: [llvm-dev] [RFC][PIR] Parallel LLVM IR -- Stage 0 -- IR extension Reply-To: In-Reply-To: <20170224221713.GA931 at arch-linux-jd.home> Ping. PS. Are there actually people interested in this? We will continue working anyway but it might not make sense to put it on reviews and announce it on the ML if nobody cares. On 02/24,

I assume the referring case is something like below, right? #pragma omp parallel num_threads(n) { #pragma omp critical { x = x + 1; } } If that is the case, the programmer is already writing the code that is not "serial equivalent". Our representation for parallelizer is %t = @llvm.region.entry()["omp.parallel"(),

So, I forwarded the request for highlighting trailing whitespaces to phabricator upstream (https://secure.phabricator.com/T11879), and upstream folks suggest we enable the Lint feature in Arcanist ( https://secure.phabricator.com/book/phabricator/article/arcanist_lint/). This will enforce the check when `arc diff` is run (reviewers wouldn't see the warnings though). There are two linters we