search for: myoption

...<- match.arg(arg3) result <- arg1 + arg2 cat(arg3, result, '\n') } myFunction2 <- function(arg1, arg2){ result <- arg1 * arg2 result } ### Working Example. ### myFunction2 works no problem myFunction2Vals <- subset(scoreConfig, Function == 'myFunction2') myOptions <- with(myFunction2Vals, paste(Argument, Value, sep = '=', collapse = ',')) eval(parse(text = paste( "myFunction2(", myOptions, ")" ))) ### myFunction1 fails myFunction1Vals <- subset(scoreConfig, Function == 'myFunction1') myOptions <- with(...

...-5,7 +5,12 @@ init: function(element, api){ var me = this; if ( google && google.maps ){ - var map = new google.maps.Map(element, {mapTypeId:google.maps.MapTypeId.ROADMAP}); + // be default no controls and road map + var myOptions = { + disableDefaultUI: true, + mapTypeId: google.maps.MapTypeId.ROADMAP + }; + var map = new google.maps.Map(element, myOptions); // deal with click @@ -28,8 +33,15 @@ }, applyOptions: function(){ - var map = this.m...

...} > > > myFunction2 <- function(arg1, arg2){ > result <- arg1 * arg2 > result > } > > > ### Working Example. > ### myFunction2 works no problem > myFunction2Vals <- subset(scoreConfig, Function == 'myFunction2') > myOptions <- with(myFunction2Vals, paste(Argument, Value, sep = '=', collapse = ',')) > eval(parse(text = paste( "myFunction2(", myOptions, ")" ))) > > > ### myFunction1 fails > myFunction1Vals <- subset(scoreConfig, Function == 'myFunction1')...

...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 up...

...during pass initialization 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..."), ); } -Andy

...again Oskar > Aaron Smith <aaron.lee.smith at gmail.com> hat am 6. Januar 2020 um 23:06 geschrieben: > > > Define your option in the backend and declare it extern in the other > files you want to use it in. > > // X86TargetMachine.cpp > cl::opt<bool> > MyOption("my new option", cl::init(true), cl::Hidden, > cl::desc("Enable my new option")); > > // X86SomeOtherFile.cpp > extern cl::opt<bool> MyOption; > if (MyOption) { > // do something > } > > On Mon, Jan 6, 2020 at 1:30 PM Craig...

...; - + if (args.zoom == ''large''){ + this.addLargeControls(); + } else { + this.addSmallControls(); + } } }, @@ -66,7 +68,7 @@ var map = this.maps[this.api]; var myOptions = { navigationControl:true, - navigationControlOptions: {style:google.maps.NavigationControlStyle.DEFAULT}, + navigationControlOptions: {style:google.maps.NavigationControlStyle.DEFAULT} }; map.setOptions(myOptions); this.addControl...

Hello, I am using lpxelinux.0 (latest stable version 6.03, using the official binaries from kernel.org) to kickstart servers as http transfers really helps over links with poor latencies... These servers are being booted in legacy mode, not in UEFI. This has worked very well until recently. Starting with RHEL 7.5, on some servers, we would see the machine rebooting while pxelinux is in the

...t" src="http://maps.google.com/maps/api/js? sensor=false"></script> <script type="text/javascript"> function initialize() { var latlng = new google.maps.LatLng(28.142722, -15.448609); //Creatin a MapOptions object with tthe required properties var myOptions = { zoom: 3, center: latlng, mapTypeId: google.maps.MapTypeId.ROADMAP }; //Creating the map var map = new google.maps.Map(document.getElementById("mapilla"), myOptions); // add the marker itself var marker = new google.maps.Marker({ position: la...

...S stack somewhere? Just some random and humble thoughts... Perhaps it would be worth some additional tests? Maybe a test with pxelinux.0 version 4.07? And using "LINUX", not "KERNEL": ### DEFAULT biginitrd PROMPT 0 LABEL biginitrd LINUX mykernel INITRD mybiginitrd APPEND myoptions ### Maybe a packet capture might reveal something about the network setup? Maybe it is not the size of the initrd file but rather a time limitation (which gets triggered by a big-enough file)? What about trying with 6.04-pre1, and/or (even better) with Debian Sid's packages and using debu...

...ll 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..."), ); > } > > -Andy >...

Hi Scott, On 11/05/13 00:09, Scott Pakin wrote: > Is it possible for a pass to get access to the command line options > passed to it? That is, if I use the CommandLine library to define > > cl::opt<int> Foo("foo", ...); > cl::opt<int> Bar("bar", ...); > cl::opt<bool> Baz("baz", ...); > > and the user runs

...not just lpxelinux.0. Alternatively (and in many cases, even better) you could try current Debian's "Unstable" packages, which are "more up-to-date" than 6.04-pre1. B_ In the configuration file, instead of using: ### LABEL mylabel KERNEL mykernel INITRD myinitrd APPEND myoptions ### try: ### LABEL mylabel LINUX mykernel INITRD myinitrd APPEND myoptions ### and/or also try: ### LABEL mylabel2 COM32 linux.c32 APPEND initrd=myinitrd myoptions ### (Reminder: use linux.c32 and the lib*.c32 modules from the same version as lpxelinux.0 and ldlinux.c32.) Using the LINUX...

CommandFlags.inc is only included by llc and opt. I think it mostly just sets things on TargetMachine and TargetOptions and connects them to command line options. Clang has its own code for setting up TargetMachine and TargetOptions. I think a lot of configuration things these days tend to be done with function attributes in IR. You can just query the function attribute wherever without any need

...lization 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..."), ); > } > > -Andy &g...

Is it possible for a pass to get access to the command line options passed to it? That is, if I use the CommandLine library to define cl::opt<int> Foo("foo", ...); cl::opt<int> Bar("bar", ...); cl::opt<bool> Baz("baz", ...); and the user runs "opt -load mypass.so -foo=123 -std-compile-opts -baz", can I somehow get a string

...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..."), ); >> }...

...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..."), ); > } Sounds good to me....

...lization 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..."), ); > } > > -Andy >...

...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..."), ); >&gt...