search for: argumnets

Hi all, I was wondering if there's any way to pass command line arguments to LLVM optimization passes when run through the opt tool. For example, suppose I register called MyPass, then I want to run opt -load libMyPass.so -MyPass 3 < input.bc and have "3" be available to MyPass as a kind of argv argumnet through some method. Or does it take a major rewrite of the opt tool

Hi It seems that survfit() doesn't accept the argumnet 'error' as below >survfit(fit, error='greenwood') Error in survfit.coxph(fit, error = "greenwood") : unused argument(s) (error ...) Isn't is allowed to do that for a coxph object? Regards Soren Windows XP, SP2 R 2.3.0

A follow-up question: Is there a way to make different passes accept one command line option that will affect all of them? For example, I'd like to have a -optStrength parameter, that can be given to all of my passes simultaneously. Thanks a lot, Guy Arnaud Allard de Grandmaison wrote: > > Hi Harel, > > Several existing passes can take command line arguments. Have a look at

Hi Harel, Several existing passes can take command line arguments. Have a look at lib/Transforms/Scalar/LoopUnrollPass.cpp for example. Its command line arguments are defined using the cl::opt objects. Best regards, -- Arnaud de Grandmaison ________________________________ From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Harel Cain Sent: Thursday, January

You could make the cl:opt object visible outside one of your passes, and use it in your other passes : in other words, it is a global variable shared between several files. Best regards, -- Arnaud de Grandmaison -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of guyadini Sent: Thursday, January 27, 2011 12:38 PM To: llvmdev at

x<-1 f<-function(){ x<-3 eval(substitute(x+y,list(y=10))) } f() #13 x<-1 f<-function(){ x<-3 eval(substitute(x+y,list(y=10)), envir = sys.frame(sys.parent())) } f() #11 x<-1 f<-function(){ x<-3 eval.parent(substitute(x+y,list(y=10))) } f()#11 the help page says: "If 'envir' is not specified, then 'sys.frame(sys.parent())', the

It would be really nice if nlm took a set of "..." optional arguments that were passed through to the objective function. This level of hacking is probably slightly beyond me: is there a reason it would be technically difficult/inefficient? (I have a vague memory that it used to work this way either in S-PLUS or in some previous version of R, but I could easily be wrong.) Here's

Hi the list, I define a method that want to change an object without assignation (foo(x) and not x<-foo(x)) using deparse and assign. But when the argument of the method does not match *exactly* with the definition of the generic function, assign does not work... Anything wrong? Christophe #------ Does not work ------#

Me again... :) Despite all of the comments made in favor of the .OGG extension, I'm still going to have to side with the "different extension" camp. There are a number of reasons for this... First off... from where I'm sitting, it doesn't matter how much of a grey-area you get into, I can't think of a single scenario where you wouldn't be able to say that it was