search for: 2mm

Hi all, It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for code generation, but both of them lead to almost...

On 09/01/2013 08:02 PM, Star Tan wrote: > Hi all, > > > It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. > > > Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for code generation, but both of them lea...

...013-09-02 17:05:52,"Tobias Grosser" <tobias at grosser.es> wrote: >On 09/01/2013 08:02 PM, Star Tan wrote: >> Hi all, >> >> >> It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. >> >> >> Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for code generation, but both...

...Tobias Grosser" <tobias at grosser.es> wrote: > >> On 09/01/2013 08:02 PM, Star Tan wrote: >>> Hi all, >>> >>> >>> It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. >>> >>> >>> Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for code generati...

...;tobias at grosser.es> wrote: >> >>> On 09/01/2013 08:02 PM, Star Tan wrote: >>>> Hi all, >>>> >>>> >>>> It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. >>>> >>>> >>>> Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for c...

...d.to.row arguments set.seed(2345) res <- matrix(sample(0:9, size=6*9, replace=TRUE), ncol=6, nrow=9) xres <- xtable(res) digits(xres) <- rep(0, 7) addtorow <- list() addtorow$pos <- list() addtorow$pos[[1]] <- c(0, 2) addtorow$pos[[2]] <- 4 addtorow$command <- c('\vspace{2mm} \n', '\vspace{10mm} \n') print(xres, add.to.row=addtorow, include.rownames=FALSE, include.colnames=TRUE, only.contents=TRUE, hline.after=c(0, 0, 9, 9)) Output (only.contents=TRUE) % latex table generated in R 2.13.2 by xtable 1.6-0 package % Fri Oct 28 11:38:10 2011 1 & 2 & 3...

...} for (i = 0; i < _PB_NI; i++) for (j = 0; j < _PB_NL; j++) { D[i][j] *= beta; for (k = 0; k < _PB_NJ; ++k) D[i][j] += tmp[i][k] * C[k][j]; } i m using following command $opt -S -O3 -force-vector-width=64 -pass-remarks=loop-vectorize -enable-load-pre=0 2mm.ll -o 2mm-64_o3.ll what is wrong here? what should i do? Please help.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180315/6bfc58d8/attachment.html>

...riginal file name plus some new information. The way I have it set up right now, I keep saving over each new graph. I can turn the history on and see them all, but I want them all to save as unique files as well. Idealy they would be "filename CHN 1mm Length Frequency", "filename CHN 2mm Length Frequency"...and so forth. Any hints? Thanks for your time. Here is what I'm using now: filenames<-dir("C:/Documents and Settings/tfish/Desktop/R/Untilted Data") for(i in filenames){data<- read.csv(i, header = TRUE, skip = 13, sep = ",") hist(data$X.mm.[da...

...for (j = 0; j < _PB_NL; j++) > { > D[i][j] *= beta; > for (k = 0; k < _PB_NJ; ++k) > D[i][j] += tmp[i][k] * C[k][j]; > } > > i m using following command > $opt -S -O3 -force-vector-width=64 -pass-remarks=loop-vectorize > -enable-load-pre=0 2mm.ll -o 2mm-64_o3.ll > > what is wrong here? what should i do? > > Please help.. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180314/cd6794d6/attachment.html>

Hi. Two questions: 1. Is this now reasonably stable for large mailboxes (c 2mm messages)? 2. Will this leave the filename in the message body unchanged? So for example if I have the same attachment called proposalfromvendor.pdf and proposaltoclient.pdf in two different emails, will the original names be kept ? Or will it replace the filename with some kind of numeric hash ?...

...e and I what I need comes in sequence. The following table is what I have for a single year. Notice that number of observations varies from day to day entire year. *Day* *Time* *Prec* Jan 1 7:00 20mm 1 7:20 15mm 1 7:30 5mm 2 6:00 10mm 2 15:00 16mm ... ... ...mm 31 7:00 2mm Feb 1 9:00 6mm 1 9:45 30mm 2 6:45 12mm 2 16:00 20mm 2 22:00 60mm *...* *...* *...mm* 28 11:30 25mm *...* *...* *...* *...mm* Dec 31 *...* *...mm* That way is hard to develop analysis comparing to another year. Thus, I would like summarize all information in a new (rea...

...oia/AMGmk/AMGmk, compile_time(+491.80%), execution_time (0%) SingleSource/UnitTests/Vector/multiplies, compile_time(+350.00%), execution_time(-13.64%) SingleSource/Benchmarks/Stanford/Puzzle, compile_time(+345.45%), execution_time(-40.91%) SingleSource/Benchmarks/Polybench/linear-algebra/kernels/2mm/2mm, compile_time(+278.95%), execution_time(0%) SingleSource/Benchmarks/Polybench/linear-algebra/kernels/3mm/3mm, compile_time(+270.73%), execution_time(0%) SingleSource/Benchmarks/Polybench/linear-algebra/kernels/syrk/syrk, compile_time(+208.57%), execution_time(0%) SingleSource/Benchmarks/Poly...

...ntly made a 64-bit build of R-2.2.1 under Solaris 9 using gcc v.3.4.2. The server has 12GB memory, 6 Sparc CPUs and plenty of swap space. I was the only user at the time of the following experiment. I wanted to benchmark R's capability to read large data files and used a data set consisting of 2MM records with 65 variables in each row. All but 2 of the variables are of the character type and the other two are numeric. The whole data set is about 600 MB when stored as plain ASCII file. The following code was used in the benchmarking runs: c = list(var1=0, var2=0, var3="", var...

...opRerolling-flt/LoopRerolling-flt -11.14% SingleSource/Benchmarks/Polybench/linear-algebra/kernels/syr2k/syr2k -11.11% MultiSource/Benchmarks/TSVC/Packing-flt/Packing-flt -10.87% MultiSource/Benchmarks/TSVC/Searching-dbl/Searching-dbl -10.87% SingleSource/Benchmarks/Polybench/linear-algebra/kernels/2mm/2mm -10.74% SingleSource/Benchmarks/Polybench/linear-algebra/kernels/doitgen/doitgen -10.66% ... Star Tan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130925/a36b76fe/attachment.html>

...ze: clang -Xclang -load -Xclang LLVMPolly.so -mllvm -polly -O3 (use polly optimization) The preliminary experimental results are as follows: (benchmarks are collected from Po | | Clang (seconds) | Polly-basic (seconds) | Polly-optimize (seconds) | Polly-load overhead | Polly-optimize overhead | | 2mm.c | 0.786 | 0.802 | 1.944 | 2.0% | 147.3% | | correlation.c | 0.782 | 0.792 | 2.005 | 1.3% | 156.4% | | gesummv.c | 0.583 | 0.603 | 1.08 | 3.4% | 85.2% | | ludcmp.c | 0.787 | 0.806 | 2.475 | 2.4% | 214.5% | | 3mm.c | 0.786 | 0.811 | 2.617 | 3.2% | 233.0% | | covariance.c | 0.73 | 0.74 | 2.294 | 1.4...

...mllvm -polly -O3 (use polly optimization) > >I believe this setup is a very good start. However, to draw useful >conclusions we probably need more information: > >1) Did you build LLVM/Polly in release mode? > >The compile times with and without Polly look very high. Compiling 2mm >with a current version of clang takes 0.076 seconds for me, whereas you >report a compile time of 0.780 seconds. This may caused by performance >differences of our machines or, what I believe is more likely, that you >did not compile LLVM and Polly in Release mode. Profiling of debug...

...t; > > > 1 > > 7:00 > > 20mm > > 1 > > 7:20 > > 15mm > > 1 > > 7:30 > > 5mm > > 2 > > 6:00 > > 10mm > > 2 > > 15:00 > > 16mm > > ... > > ... > > ...mm > > 31 > > 7:00 > > 2mm > > Feb > > 1 > > 9:00 > > 6mm > > 1 > > 9:45 > > 30mm > > 2 > > 6:45 > > 12mm > > 2 > > 16:00 > > 20mm > > 2 > > 22:00 > > 60mm > > *...* > > *...* > > *...mm* > > 28 > > 1...

...-load -Xclang LLVMPolly.so -mllvm -polly -O3 (use polly optimization) I believe this setup is a very good start. However, to draw useful conclusions we probably need more information: 1) Did you build LLVM/Polly in release mode? The compile times with and without Polly look very high. Compiling 2mm with a current version of clang takes 0.076 seconds for me, whereas you report a compile time of 0.780 seconds. This may caused by performance differences of our machines or, what I believe is more likely, that you did not compile LLVM and Polly in Release mode. Profiling of debug builds may give...

...just choose the Mediabench from LLVM-testsuite. The preliminary results of Polly compiling overhead is listed as follows: Table 1: Compiling time overhead of Polly for PolyBench. | | Clang (econd) | Polly-load (econd) | Polly-optimize (econd) | Polly-load penalty | Polly-optimize Penalty | | 2mm.c | 0.155 | 0.158 | 0.75 | 1.9% | 383.9% | | correlation.c | 0.132 | 0.133 | 0.319 | 0.8% | 141.7% | | geummv.c | 0.152 | 0.157 | 0.794 | 3.3% | 422.4% | | ludcmp.c | 0.157 | 0.159 | 0.391 | 1.3% | 149.0% | | 3mm.c | 0.103 | 0.109 | 0.122 | 5.8% | 18.4% | | covariance.c | 0.16 | 0.163 | 1.346 | 1.9...

On 08/10/2013 06:59 PM, Star Tan wrote: > Hi all, > > I have evaluated Polly's performance on LLVM test-suite with latest LLVM (r188054) and Polly (r187981). Results can be viewed on: http://188.40.87.11:8000. Hi Star Tan, thanks for the update. > There are mainly five new tests and each test is run with 10 samples: > clang (run id = 27): clang -O3 > pollyBasic (run id =