search for: optimzi

...;> Hello LLVMers, >> >> I am developing hardware generation tool which converts C/C++ application to >> hardware which is not a Pass but a separate project. I am going to use LLVM >> as front-end optimization tool. I am curious how I can invoke the LLVM >> front-end optimziations and then, get the pointer of LLVM IR data generated >> by the front-end. I would like to perform some optimziations on the IR. Can >> anybody please direct me to some example codes or documentation about that? >> >> Thank you. >> _________________________________...

Hello LLVMers, I am developing hardware generation tool which converts C/C++ application to hardware which is not a Pass but a separate project. I am going to use LLVM as front-end optimization tool. I am curious how I can invoke the LLVM front-end optimziations and then, get the pointer of LLVM IR data generated by the front-end. I would like to perform some optimziations on the IR. Can anybody please direct me to some example codes or documentation about that? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... UR...

...ype-legalized selection DAG: t22: i8 = srl t19, Constant:i64<1> t40: i8 = xor t22, Constant:i8<1> t31: ch = brcond t18, t40, BasicBlock:ch<if.else 0xa5f8d48> t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> The truncate is now gone. Next we have the Optimzied type-legalized DAG: t22: i8 = srl t19, Constant:i64<1> t43: i8 = setcc t22, Constant:i8<1>, setne:ch t31: ch = brcond t18, t43, BasicBlock:ch<if.else 0xa5f8d48> t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> The *xor* has been replaced with a *set...

...t22: i8 = srl t19, Constant:i64<1> > t40: i8 = xor t22, Constant:i8<1> > t31: ch = brcond t18, t40, BasicBlock:ch<if.else 0xa5f8d48> > t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> > > The truncateis now gone. > > Next we have the Optimzied type-legalized DAG: > > t22: i8 = srl t19, Constant:i64<1> > t43: i8 = setcc t22, Constant:i8<1>, setne:ch > t31: ch = brcond t18, t43, BasicBlock:ch<if.else 0xa5f8d48> > t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> > > The***...

Hello, I'm trying to use fitdistr() from the MASS package to fit a gamma distribution to a set of data. The data set is too large (1167 values) to reproduce in an email, but the summary statistics are: Min. 1st Qu. Median Mean 3rd Qu. Max. 116.7 266.7 666.7 1348.0 1642.0 16720.0 The call I'm trying to make is: fitdistr(x,"gamma") and the error is: Error in optim(x =

...t22: i8 = srl t19, Constant:i64<1> > t40: i8 = xor t22, Constant:i8<1> > t31: ch = brcond t18, t40, BasicBlock:ch<if.else 0xa5f8d48> > t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> > > The truncate is now gone. > > Next we have the Optimzied type-legalized DAG: > > t22: i8 = srl t19, Constant:i64<1> > t43: i8 = setcc t22, Constant:i8<1>, setne:ch > t31: ch = brcond t18, t43, BasicBlock:ch<if.else 0xa5f8d48> > t33: ch = br t31, BasicBlock:ch<if.then 0xa5f8c98> > > The *x...

...however, there is a value in the standalone LD, and in many cases vectorization oriented LD can still happen there. Performing LD in VPlan-to-VPlan would improve precision of the cost modeling, but given that vectorizer's cost model is "ball park"-based to begin with (we have a lot of optimziers running downstream!), having extra precision will be worth only by that much. I have a thought about moving vectorizer's analysis part (all the way to cost model) into Analysis. When extra precision is desired, we can utilize such an (heavier weight) Analysis. In short, my preference is to...

Having finally found some time to work on this project, I'm currently looking at mechanisms of augmenting LLVM to catch out-of-bounds pointer references. For a variety of reasons, I don't think the approach taken by the Safecode project is appropriate for mine -- particularly, I have no requirement to interface to external code (all code in the system will either be compiled using

Hi, I found with the help of the optimization remarks a loop that could not be vectorized, but if loop distribution was enabled this may happen, which it in fact did with a very significant benchmark improvement (~25%). I tried (on SystemZ) to enable this pass, and found that it only affected a handful of files on SPEC. This means I could enable this without worrying about any regressions on

Hi, I don''t know if this has been discussed before, but have you thought about adding LZO compression to ZFS? One zfs-fuse user has provided a patch which implements LZO compression, and he claims better compression ratios *and* better speed than lzjb. The miniLZO library is licensed under the GPL, but the author specifically says that other licenses are available by request. Has this