search for: sopt

...tor dim(y) # [1] 49 1 # application of LASSO regression where y is response and X2 is a design matrix data1<-data.frame(y,X2=I(X2)) lasso_res=lassoCV(y~X2,data=data1,K=10,fraction=seq(0.1,1,by=0.1),use.Gram=FALSE) # to get optimum value of Cross Validation lasso_coef=lassocoef(y~X2,data=data1,sopt=lasso_res$sopt,use.Gram=FALSE) # to get the coefficients [[alternative HTML version deleted]]

...uot; for this script; there's a large amount of shell-fu (not clever "tricks", but actual "how to make a robust, readable, portable shell script"-fu) in there that you will want to imitate. > LLVMHOME=/home/projects/llvm/upstream/llvm-trunk-build/Release+Asserts/bin > SOPTS="-generate-ppc-fp128" > TOPTS="-mtriple=powerpc64-unknown-linux-gnu -mcpu=pwr7" Hardcoding these seems a bit "wrong". Are there any reasonable defaults we can use? ((pwd, empty, host triple) for the three options, respectively, might be reasonable?). -- Sean Silv...

I have been working on a patch to add support for max/min reductions in LoopVectorize. One of the comments that came up in review is that the implementation could be simplified (and less fragile) if max and min intrinsics were recognized rather than looking for compare-select sequences. The suggestion was to change compare-selects into max and min intrinsic calls during instcombine. The

...n remote_loop(conspty, remote); + + init_term(fileno(stdin), &attr); + + in = fileno(stdin); + out = fileno(stdout); + + ret = console_loop(conspty, in, out, 0); + + restore_term(in, &attr); + + return ret; +} + int main(int argc, char **argv) { - struct termios attr; int domid; - char *sopt = "h"; + char *sopt = "rp:gndh"; int ch; int opt_ind=0; struct option lopt[] = { + { "remote", 0, NULL, ''r'' }, + { "port", 1, NULL, ''p'' }, + { "gateway", 0, NULL, ''g'' }, + { "n...

A few people have requested features; I've implemented them in this updated version (attached). Do you think this is worth putting in the repo somewhere? -Hal ----- Original Message ----- > Hi, > > I wrote a small script in order to stress test llc using test cases > generated by llvm-stress. When it finds a case where llc seems to > have crashed, it greps the output for

..."tricks", but > actual "how to make a robust, readable, portable shell script"-fu) > in there that you will want to imitate. Sounds good. I'll look at it. > > > > > LLVMHOME=/home/projects/llvm/upstream/llvm-trunk-build/Release+Asserts/bin > > SOPTS="-generate-ppc-fp128" > > TOPTS="-mtriple=powerpc64-unknown-linux-gnu -mcpu=pwr7" > > > Hardcoding these seems a bit "wrong". Are there any reasonable > defaults we can use? ((pwd, empty, host triple) for the three > options, respectively, might...

Hi, I wrote a small script in order to stress test llc using test cases generated by llvm-stress. When it finds a case where llc seems to have crashed, it greps the output for Assertion, LLVM ERROR, etc., removes things that look like hex numbers and ID numbers, and then checksums the resulting text. In this way, it can automatically categorize different bugs into different subdirectories. I