search for: innerations

I was looking at the ClassTemplatePartialSpecializationDecl::getInstantiatedFromMember documentation, in the included example it says: "(..) the instantiation of Outer<float>::Inner<int*> will end up instantiating the partial specialization Outer<float>::Inner<U*> (...)". To understand the concept better, I dumped the AST for the following code:

>> What needs to be done (on a high level) in order to have the auto vectorizer succeed on the test function as given erlier? > Maybe you could rewrite the loop in a way that will expose contiguous memory accesses. Is this something you could do ? > Hi Nadav, the only option I see is to unroll the loop by hand. Since the array access is consecutive over 4 loop iterations I gave it a

On Oct 30, 2013, at 6:10 PM, Frank Winter <fwinter at jlab.org> wrote: > the only option I see is to unroll the loop by hand. Since the array access is consecutive over 4 loop iterations I gave it a try and unrolled the loop by a factor of 4. Which gives the following array accesses: > > loop iter 0: > index_0 = 0 index_1 = 4 > index_0 = 1 index_1 = 5 > index_0 = 2

Hi, TL;DR: A loop doesn't get vectorized due to the interaction of loop- rotate, licm and instcombine. What to do about it? Full story: In the benchmarks for our out-of-tree target we have a case that we would like to get vectorized, but currently it isn't. I've done some digging to see why and have some kind of idea what prevents it, but I don't know what the best way to fix

I'm using R Version 2.6.1 under Windows XP. > search() [1] ".GlobalEnv" "s" "s" "package:cairoDevice" [5] "package:datasets" "package:foreign" "package:graphics" "package:grDevices" [9] "package:gWidgetsrJava"

How would following Pascal code be translated to LLVM? procedure outer(a: integer): integer; procedure inner(b: integer): integer; begin return a + b end; begin return inner(a) end; If outer(10) is called, it returns 20. The problem here is that inner has access to the locals and formal arguments of outer. I do not see any direct support for this. It could be

I'm having an issue where a certain set of types and insert/extractvalue are producing the incorrect values. It appears as though extractvalue getting my sub-structure is not getting the correct data. I have these types: %outer = type { i32, %inner, i1 } %inner = type { double, i32 } The trouble is that when I have a value of type %outer then proceed to extract the components of the

Here's a fun spin on this same topic (I can't file a bug at this moment since llvm.org is down). Consider: define i32 @x(i32* %x, i1* %y) { entry: br label %loop loop: %v = phi i32 [ 0 , %entry ], [ %v.inc, %exit.inner ], [ %v, %loop ] %c = load volatile i1, i1* %y br i1 %c, label %exit.inner, label %loop exit.inner: %c1 = load volatile i1, i1* %y %x.val = load i32, i32*

This is my simple code, my intention is to let the inner function browse the objects in the outer function. ####################### tk1 <- function() { tk2 <- function() { inner <- 3 list2 <- ls() #list objects in fuction tk2 print("**** inner objects ****") print(list2) #list objects in fuction tk1 list_parent <- ls(parent.frame())

I tried the following on the hand-unrolled loop: const std::uint64_t ir0 = i*8+0; // working const std::uint64_t ir0 = i%4+0; // working const std::uint64_t ir0 = (i+0)%4; // not working '+0' means +1,+2,+3 in the unrolled iterations. 'Working' means the SLP vectorizer succeeded. Thus, when working 'towards' the correct index function, auto

----- Original Message ----- From: "Jeff Cohen" <jeffc at jolt-lang.org> To: <LLVMdev at cs.uiuc.edu> Sent: Saturday, August 21, 2004 7:35 PM Subject: [LLVMdev] How to handle nested procedures? > How would following Pascal code be translated to LLVM? > > procedure outer(a: integer): integer; > procedure inner(b: integer): integer; > begin >

Hi Steve it seems the general consensus is that the patch feels like a work-around for a problem with LSR (and possibly other loop transformations) that introduces redundant instructions. It is probably best to file a bug and a few of your test cases. Thanks Gerolf > On Sep 10, 2015, at 4:37 PM, Steve King via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Thu, Sep 10, 2015

Hello all, Apologize for the newbie question. What's the easiest way to do a SQL inner table join in R? Say I have a table containing column names A, B, C and another which has columns named C, D, E. I would like to do an inner table join on C and produce a table A, B, C, D, E. thanks a lot, N. -- View this message in context:

Hi Frank, > We are looking at a variety of target architectures. Ultimately we aim to run on BG/Q and Intel Xeon Phi (native). However, running on those architectures with the LLVM technology is planned in some future. As a first step we would target vanilla x86 with SSE/AVX 128/256 as a proof-of-concept. Great! It should be easy to support these targets. When you said wide-vectors I assumed

Dear list, I have a problem with nested functions and I don't manage to get it solved. I know I should be looking in environments, and I have tried a lot, but it keeps on erroring. An easy version of the problem is as follows: innerfunction<-function() { print(paste(a, " from inner function")) print(paste(b, " from inner function")) setwd(wd) }

On Sat, 21 Aug 2004 20:35:35 -0500 "Patrick Meredith" <pmeredit at uiuc.edu> wrote: > > ----- Original Message ----- > From: "Jeff Cohen" <jeffc at jolt-lang.org> > To: <LLVMdev at cs.uiuc.edu> > Sent: Saturday, August 21, 2004 7:35 PM > Subject: [LLVMdev] How to handle nested procedures? > > > > How would following Pascal

-----Urspr?ngliche Nachricht----- Von: Matthias Wendel [mailto:office at matthiaswendel.de] Gesendet: Mittwoch, 9. Januar 2008 13:06 An: 'r-help-bounces at r-project.org' Cc: 'Gabor Grothendieck' Betreff: AW: [R] subsetting Thank you, Gabor, for this clarificaton. This is very helpful f?r me. Matthias -----Urspr?ngliche Nachricht----- Von: Gabor Grothendieck

I also saw this issue before. Llvm seems have trouble returning general struct values from functions. One easy workaround is to use packed struct type. Hope this helps. -Peng On Sunday, December 30, 2012, edA-qa mort-ora-y wrote: > I'm having an issue where a certain set of types and insert/extractvalue > are producing the incorrect values. It appears as though extractvalue >

Hi all, It looks like the induction variable simplification pass prefers doing a zero-extension to compute the wider trip count of loops when extending the IV. This can sometimes result in loss of information making ScalarEvolution's analysis conservative which can lead to missed performance opportunities. For example, consider this loopnest- int i, j; for(i=0; i< 40; i++) for(j=0;

Hi Reid, I've been working on the outlining code and have a prototype that produces what I want for a simple case. Now I'm thinking about the heuristics for recognizing the various logical pieces for C++ exception handling code and removing them once they’ve been cloned. I've been working from various comments you've made earlier in this thread, and I'd like to run something