search for: opimised

Displaying 5 results from an estimated 5 matches for "opimised".

Did you mean: optimised
2009 Nov 19
1
optim(.. ,"SANN",..)
...t;-c(1,1,1,1,1,1,1,1,1,1) res <- optim(v, fr, method="SANN", control=list(maxit=200, temp=20,v)) I get the following error: Error in prod(..., na.rm = na.rm) : invalid 'type' (list) of argument I'm not sure if its because this function is too disjoint to be opimised using SANN or I am not using optim properly. Any help or suggestions would be appreciated. Thanks
2002 Nov 22
8
Samba newbie question...
Can Samba be used as a complete replacement for a Windows 2000 Active Directory server? I have some vague notion that this can be accomplished by using a combination of OpenLDAP, Samba, MIT Kerberos, and the OpenAFS file system. To say the least, the descriptions I have found have been vague as to whether or not I will be able to completely replace the functionality of an Active Directory server
2020 May 20
2
LV: predication
Hi Ayal, Let me start with commenting on this: > A dedicated intrinsic that freezes the compare instruction, for no apparent reason, may potentially cripple subsequent passes from further optimizing the vectorized loop. The point is we have a very good reason, which is that it passes on the right information on the backend, enabling opimisations as opposed to crippling them. The compare
2020 May 21
2
LV: predication
> The compare of interest is clear, I think. It compares a Vector Induction Variable with a broadcasted loop invariant value, aka the BTC. Obtaining the latter operand is the goal, clearly, but to do so, the former operand needs to be recognized as a VIV. Yep, exactly that. > What if this compare is not generated by LV’s fold-tail-by-masking transformation? Not sure I completely follow
2020 May 01
5
LV: predication
Hi Eli, > The problem with your proposal, as written, is that the vectorizer is producing the intrinsic. Because we don’t impose any ordering on optimizations before codegen, every optimization pass in LLVM would have to be taught to preserve any @llvm.set.loop.elements.i32 whenever it makes any change. This is completely impractical because the intrinsic isn’t related to anything