search for: myopt

Is there a simple way to require a pass, e.g., Reg2Mem/Mem2Reg, to run before/after my transformation pass? Or do I do something like: struct myOpt { myOpt() { mBefore = createDemoteRegisterToMemoryPass(); mAfter = createPromoteMemoryToRegisterPass(); } getAnalysisUsage(AU) { AU.addRequired(my stuff); mBefore.getAnalysisUsage(AU); mAfter.getAnalysisUsage(AU); } runOnFunction(aF) { changed = mBefore(F); d...

...} ### Function to be optimized; ### param is a vector of 2 values (.alpha and .beta) myfunc <- function(param){ myalpha<-param[1] mybeta<-param[2] IVtransf<-transformIV(myalpha, mybeta) sumofdevs<-mysum(myIV=IVtransf,myDV=DV) return(sumofdevs) } # Optimizing using optim: myopt <- optim(fn=myfunc, par=c(0.1,max(IV)), method="L-BFGS-B", lower=0) (myopt) myfunc(myopt$par) ## Comparing this solution to Excel Solver solution: myfunc(c(0.888452533990788,94812732.0897449)) -- Dimitri Liakhovitski marketfusionanalytics.com

...m function I get an error saying that the curl option is not recognized. I have tried 3 different ways of instructing the curlPerform function to use the .netrc file (in the .opts, curl handle and the ... argument) but got the same error message each time. # Failed attempt using .opts construct myopts <-curlOptions(netrc=1) curlPerform("http://www.omegahat.org/RCurl/testPassword/index.html", .opts=myopts) # Failed attempt using curl handle handle <- getCurlHandle(netrc=1) curlPerform("http://www.omegahat.org/RCurl/testPassword/index.html", curl=handle) # Failed att...

...imple way to require a pass, e.g., Reg2Mem/Mem2Reg, to > run before/after my transformation pass? Or do I do something like: One simplest way is to handle this is to add these passes around your pass in the pass manager. pm.add(Reg2Mem) pm.add(MyPass) pm.add(Mem2Reg) > > > struct myOpt { > myOpt() { > mBefore = createDemoteRegisterToMemoryPass(); > mAfter = createPromoteMemoryToRegisterPass(); > } > > getAnalysisUsage(AU) { > AU.addRequired(my stuff); > mBefore.getAnalysisUsage(AU); > mAfter.getAnalysisUsage(AU); > } >...

...e storage for the options being hold in the context somehow (old memories, not sure about the details). CC Chris who likely has more information (and possibly pointers). — Mehdi > So here comes the strawman: > > > static Statistic NumBlips("blips"); > static cl::opt MyOpt("my-cool-option", cl::desc("bla")); > static cl::opt AnotherOpt("bla", cl::desc("foo bar")); > // Note that the constructors of Statistic and cl::opt would be reworked to be pure constexpr and do not run any code > > static void init_globals() {...

...r/linker nerd in me would love doing that, I could see this being very tricky to pull off consistenly on all platforms. We should not forget that there is a portable and proven solution: Just write the code! So here comes the strawman: static Statistic NumBlips("blips"); static cl::opt MyOpt("my-cool-option", cl::desc("bla")); static cl::opt AnotherOpt("bla", cl::desc("foo bar")); // Note that the constructors of Statistic and cl::opt would be reworked to be pure constexpr and do not run any code static void init_globals() { NumBlips.init();...

...global. - Matthias [1] Please someone please give us an easier time to access old mails when you just have the old link... > > Mehdi > > > >> So here comes the strawman: >> >> >> static Statistic NumBlips("blips"); >> static cl::opt MyOpt("my-cool-option", cl::desc("bla")); >> static cl::opt AnotherOpt("bla", cl::desc("foo bar")); >> // Note that the constructors of Statistic and cl::opt would be reworked to be pure constexpr and do not run any code >> >> static void i...

...taking lli, copying it, and tuning it into the tool that you'd like it to be. I'd like to keep lli simple and focused on what it does, which is provide primitive command line access to the jit/interpreter. Note that you can potentially just use a shell script which does: opt foo.bc -myopt | lli ... -Chris

Greetings, I have a plan to use LLVM to undertake runtime optimisation of computational chemistry programs. As part of this, I'd like to be able to invoke lli and pass it a list of passes to run, in the manner of opt. For example: > lli -load=llvm/mem_trace_pass/bin/lib/hello.so -hello ./my_bitcode.bc The current implementation of lli (updated from SVN as of three nights ago)

Given that LLVM has so many auto-registration systems (cl::opt, target registry, pass registry, statistics, I'm sure there's more), maybe we should spend the time to build an auto-registration system that doesn't involve static constructors? It needs custom code for every supported object file format, and is hard to get right when DSOs are involved, but in the long run it's

...Group's removeTimer method is never called, nor is it's destructor (but it's constructor is). On Wed, Jun 1, 2011 at 11:51 AM, Andrew Clinton <andrew at sidefx.com> wrote: > I got it working with this: > >     int          argc = 2; >     const char  *argv[2] = {"myopt", "-time-passes"}; > >     cl::ParseCommandLineOptions(argc, (char **)argv, "my optimizer"); > > On 06/01/2011 01:19 PM, Michael Ilseman wrote: >> I have some PassManagers, and I would like to output timing data for >> how long each pass takes to exe...

I got it working with this: int argc = 2; const char *argv[2] = {"myopt", "-time-passes"}; cl::ParseCommandLineOptions(argc, (char **)argv, "my optimizer"); On 06/01/2011 01:19 PM, Michael Ilseman wrote: > I have some PassManagers, and I would like to output timing data for > how long each pass takes to execute with a separate appl...

...s never called, nor is it's > destructor (but it's constructor is). > > On Wed, Jun 1, 2011 at 11:51 AM, Andrew Clinton<andrew at sidefx.com> wrote: >> I got it working with this: >> >> int argc = 2; >> const char *argv[2] = {"myopt", "-time-passes"}; >> >> cl::ParseCommandLineOptions(argc, (char **)argv, "my optimizer"); >> >> On 06/01/2011 01:19 PM, Michael Ilseman wrote: >>> I have some PassManagers, and I would like to output timing data for >>> how lo...

I have some PassManagers, and I would like to output timing data for how long each pass takes to execute with a separate application using the API, rather than through an llvm tool. Unfortunately, I'm having trouble seeing how to use the existing facilities without using opt. Setting llvm::TimePassesIsEnabled before creating the PassManagers doesn't seem to output anything, though it is

...ve us an easier time to access old mails when you just have the old link... > > >> >> Mehdi >> >> >> >>> So here comes the strawman: >>> >>> >>> static Statistic NumBlips("blips"); >>> static cl::opt MyOpt("my-cool-option", cl::desc("bla")); >>> static cl::opt AnotherOpt("bla", cl::desc("foo bar")); >>> // Note that the constructors of Statistic and cl::opt would be reworked to be pure constexpr and do not run any code >>> >>&g...

My needs are far more modest than Capistrano''s capabilities. Also, when working in a shared hosting environment, the Capistrano model can be outside the capabilities allowed by the Web host. I simply need to push selected directories (on a changed-file basis) out to a server. I have about 80% of the code written to do this (I''m considering YAC for the name, with a nod to

...zation with all the convenient flags and parameters, but refer to a globally defined option storage that enforces the singleton and provides visibility. As long as pass initialization happens before parseCommandLine, usage should be consistent. > > Strawman: > > cl::optval<bool> MyOption; // Just the storage, no initialization. > > MyPass() { > // Only registers an option with the same optval once. > Option cl::registerOpt(MyOption, cl::init(false), cl::Hidden, > cl::desc("Descriptive string..."), ); > } Given Chandler's...

Is there a way to throttle the firing of updater requests easily with Prototype? Thanks, mark

I was adding a new option for our backend, and because of the nature of the option I wanted to use an 'enum', something like: enum Direction { left, right, up, down }; cl:opt<Direction> myOpt("option-switch", cl::init(up), cl::desc("what it does"), cl::Hidden); This bit is fine, but then I wanted to change it on the command-line to 'clang' and tried: clang ... -mllvm -option-switch=3 ... but that doesn't work, and I get something like "inval...

...>> This is not a bug report, rather than some remarks as a >> "request for comments": >> >> It is clear that options( foo = bar ) >> sets the option and also updates the builtin() .Options list : >> >> > options(myopt = pi) >> > .Options$my >> [1] 3.14159265 >> >> In S-plus, it was (is) possible to use .Options locally in a function >> frame in order to just affect some options during evaluation of that >> function. Ross> I have made some ch...