search for: interchang

...d not go very well. > > > I filed https://bugs.llvm.org/show_bug.cgi?id=47705 <https://bugs.llvm.org/show_bug.cgi?id=47705> to keep track of the issue. > > While the code for the initialization is not ideal, it appears the main issue causing the slowdown is the fact that GCC interchanges the main loops, but LLVM does not. After interchanging, the memory access patterns are completely different (and it also probably slightly defeats the purpose of the benchmark). > > There’s also an issue with SROA which splits a nice single consecutive llvm.memcpy into 3 separate ones. Wit...

Hi, When I test "matmul" in the polly directory, I get the following performance data: //=============================== --> 12. Compare the runtime of the executables time ./matmul.normalopt.exe 0:23.53 real, 23.48 user, 0.00 sys time ./matmul.polly.interchanged.exe 0:22.86 real, 22.82 user, 0.01 sys time ./matmul.polly.interchanged+tiled.exe 0:22.87 real, 22.83 user, 0.00 sys time ./matmul.polly.interchanged+tiled+vector.exe 0:22.53 real, 22.48 user, 0.02 sys time ./matmul.polly.interchanged+tiled+vector+openmp.exe 0:05.88 real, 46.71 user, 0.02 sys //=...

...'0')),k:50.000817634746205,l:'4',n:'0',o:'',s:0,t:'0')),l:'2',n:'0',o:'',t:'0')),version:4 I was thinking that modern compilers are optimizing such cases very aggressively. I quickly checked gcc, there is special option -floop-interchange, but it requires properly configured gcc compiler with Graphite infrastructure enabled. I didn't have that at hand, so I just stopped right there. Loop has no side effects and arrays do not alias, so from my point of view it's safe to do interchange here. I tried different march options a...

Are IVR and "Auto Attendant" interchangeable terms? They both do the "Press 1 for" thing. Sales is asking me how to word it and I've always used both terms interchangeably.

unsigned int and FLAC__uint32 are used interchangeably, leading to warnings with platforms (e.g. djgpp) where int32_t is long: bitreader.c: In function `FLAC__bitreader_read_rice_signed': bitreader.c:721: warning: passing arg 2 of `FLAC__bitreader_read_unary_unsigned' from incompatible pointer type bitreader.c: In function `FLAC__bitreade...

On 1/14/17, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Ozkan Sezer wrote: > >> unsigned int and FLAC__uint32 are used interchangeably, leading to >> warnings with platforms (e.g. djgpp) where int32_t is long: > > Is `sizeof int == 4` though? Yes, obviously it is > I couldn't image FLAC working correctly > if it wasn't. > > Erik

Hi Tobias, I think that we could split a patch that contains an implementation of tiling, interchanging and unrolling of specific loops into three separate patches: 1. The first one adds a class that describes a processor model. It also adds a new command line parameter that contains all necessary parameters of a target architecture, which are used to construct objects of the class. 2. The secon...

...[Proposal][RFC] Cache aware Loop Cost Analysis > > Hi, > > This is a proposal about implementing an analysis that calculates loop > cost based on cache data. The primary motivation for implementing this is > to write profitability measures for cache related optimizations like > interchange, fusion, fission, pre-fetching and others. > > I have implemented a prototypical version at > http://reviews.llvm.org/D21124. > > I quick comment on your pass: You'll also want to add the ability to get > the loop trip count from profiling information from BFI when available...

...Loop Cost Analysis >> >> Hi, >> >> This is a proposal about implementing an analysis that calculates loop >> cost based on cache data. The primary motivation for implementing this is >> to write profitability measures for cache related optimizations like >> interchange, fusion, fission, pre-fetching and others. >> >> I have implemented a prototypical version at >> http://reviews.llvm.org/D21124. >> >> I quick comment on your pass: You'll also want to add the ability to get >> the loop trip count from profiling information...

Hi Roman, On Tue, May 31, 2016 at 9:57 AM, Roman Gareev <gareevroman at gmail.com> wrote: > Hi Tobias, > > I think that we could split a patch that contains an implementation of > tiling, interchanging and unrolling of specific loops into three > separate patches: > > 1. The first one adds a class that describes a processor model. It > also adds a new command line parameter that contains all necessary > parameters of a target architecture, which are used to construct > object...

...w the analysis calculates the result). The analysis result is specific to each loop in its loop nest. Reference groups are necessary during cost computation only. > > You could probably describe how you envision this analysis would be used > with something like Loop Fusion. > For Loop Interchange, the cost calculated for each loop can provide a desired ordering of the loops. Loop interchange can start interchanging the loops to match the desired order iff interchange legality check passes. Eg: For matrix multiplication case, for (i = 0 to 5000) for (j = 0 to 5000)...

With primitive types, I can interchange literal usage and type aliases in IR: %mytype = type i32 define void @foo(%mytype* %ptr) { %t1 = load *%mytype** %ptr store i32 *%t1*, *i32** %ptr ret void } But for structs, I cannot: %mytype = type { i32, i32 } define void @foo(%mytype* %ptr) { %t1 = load *%mytype** %ptr store* {...

...tructType, is never uniqued against other identified types nor literal types, aka unnamed StructType(s)." ? See also; http://blog.llvm.org/2011/11/llvm-30-type-system-rewrite.html ...Takumi 2012/12/30 Justin Holewinski <justin.holewinski at gmail.com>: > With primitive types, I can interchange literal usage and type aliases in > IR: > > %mytype = type i32 > > define void @foo(%mytype* %ptr) { > %t1 = load %mytype* %ptr > store i32 %t1, i32* %ptr > ret void > } > > But for structs, I cannot: > > %mytype = type { i32, i32 } > > define voi...

Ozkan Sezer wrote: > > Ozkan Sezer wrote: > > > >> unsigned int and FLAC__uint32 are used interchangeably, leading to > >> warnings with platforms (e.g. djgpp) where int32_t is long: > > > > Is `sizeof int == 4` though? > > Yes, obviously it is Well I've just pushed a patch that purges the code base of `unsigned`. Please test and let us know how it goes. Erik --...

Suppose x and y are numeric vectors of the same length. plot(x,y) #scatterplot lmObj1 <- lm(y~x) # best fit line abline(lmObj1) # good lmObj2 <- lm(x~y) #get best fit but with axes interchanged abline(lmObj2) # not what I want. I want the correct line, drawn on the same graph, but with # response and predictor variables interchanged One way to proceed would be to extract the intercept and slope from lmObj2 and then do the arithmetic to draw the correct line. I'm...

On 1/14/17, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Ozkan Sezer wrote: > >> > Ozkan Sezer wrote: >> > >> >> unsigned int and FLAC__uint32 are used interchangeably, leading to >> >> warnings with platforms (e.g. djgpp) where int32_t is long: >> > >> > Is `sizeof int == 4` though? >> >> Yes, obviously it is > > Well I've just pushed a patch that purges the code base of `unsigned`. > Please test and le...

Hi, This is a proposal about implementing an analysis that calculates loop cost based on cache data. The primary motivation for implementing this is to write profitability measures for cache related optimizations like interchange, fusion, fission, pre-fetching and others. I have implemented a prototypical version at http://reviews.llvm.org/D21124. The patch basically creates groups of references that would lie in the same cache line. Each group is then analysed with respect to innermost loops considering cache lines. Pena...

...t(x = dD, y = dCu65, data = tur, color = mine) print(p) # simple bivariate plot of the data; looks fine mod1 <- Mclust(tur[,2:3]) mod1$G mod2 <- Mclust(tur[,3:2]) mod2$G One can use coordProj to see the clusters found, but the basic result is that mclust found 3 clusters in mod1, but if you interchange the x and y columns it finds 7 clusters (mod2). Since this is bivariate data, I find this result pretty strange. The only thing I can think of is that it has something to do with how the algorithm is seeded, but that isn't too convincing. Since I couldn't believe my eyes, I made up some...

lvqcl wrote: > Is it Ok to pass FLAC__int32* in a function that expects int* ? Well FLAC__int32 is just a 32 bit integer and on all the platforms/ architecures/compilers that FLAC supports FLAC__int32 and int are the same. As for pointers, all pointers are the same until you try an increment them. If you have some type, lets call it sometype_t, and a pointer to types of sometype_t :

Erik de Castro Lopo wrote: > Well FLAC__int32 is just a 32 bit integer and on all the platforms/ > architecures/compilers that FLAC supports FLAC__int32 and int are > the same. > > Personally I think the FLAC__xxxx stuff should go, to be replaced with > C standard int32_t, uint32_t, int16_t etc, at least for internal code. > I am slowly doing that when I touch code. > >