search for: createopt

...tic initialized cl::opt objects with a single >> static initialized OptionRegistry. >> >> With this change options can be constructed during initialization. For the >> example option above the pass initialization would get a line like: >> >> cl::OptionRegistry::CreateOption<bool>("ScalarizeLoadStore", >> "scalarize-load-store", cl::Hidden, cl::init(false), >> cl::desc("Allow the scalarizer pass to scalarize loads and store")); >> >> >> Also the pass would add a boolean member to store the value o...

...f options. >> The ones we want to expose to users and the ones which we use for >> testing llvm itself. The options we want to expose should be just >> constructor arguments. With that distinction we should be able to just >> not use the options added by cl::OptionRegistry::CreateOption unless >> cl::ParseCommandLineOptions is called. WebKit like clients would just >> not call cl::ParseCommandLineOptions. Would that work? >> >> >> This is actually how some of our internal clients are already working. There >> are a few caveats with this app...

...ones we want to expose to users and the ones which we use for >>>> testing llvm itself. The options we want to expose should be just >>>> constructor arguments. With that distinction we should be able to just >>>> not use the options added by cl::OptionRegistry::CreateOption unless >>>> cl::ParseCommandLineOptions is called. WebKit like clients would just >>>> not call cl::ParseCommandLineOptions. Would that work? >>>> >>>> >>>> This is actually how some of our internal clients are already working. There...

...the OptionRegistry. This will replace the 100’s of static initialized cl::opt objects with a single static initialized OptionRegistry. With this change options can be constructed during initialization. For the example option above the pass initialization would get a line like: cl::OptionRegistry::CreateOption<bool>("ScalarizeLoadStore", "scalarize-load-store", cl::Hidden, cl::init(false), cl::desc("Allow the scalarizer pass to scalarize loads and store")); Also the pass would add a boolean member to store the value of the option which would be initialized in t...

...code to update the field has no effect. Can someone tell me why? For completeness, I created a simple test rails application (bugtest) to demonstrate. The applicable files/code are as follows: ---------- bugtest/db/migrate/001_create_options.rb <--- Original table definition ---------- class CreateOptions < ActiveRecord::Migration def self.up create_table :options do |t| t.string :name t.boolean :is_deleted, :default => false, :null => false t.timestamps end end def self.down drop_table :options end end ---------- bugtest/db/migrate/002_add_delete...

> On Aug 19, 2014, at 1:32 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >>> * Nobs for which there is not a single right answer for all users. >>> There are very few of these currently and we expect it to remain like >>> that. These should not use cl::opt or static storage at all. They >>> should be an option passed to the

On 8/21/23 11:53, Jones Syue ??? via samba wrote: >> OH - that's *really* interesting ! I wonder how it is >> changing the SMB3+ redirector to do this ? > > It looks like applications could do something and give a hint to SMB3+ > redirector, so far not quite sure how to make it, > per process monitor (procmon) could show that write I/O size seems > could be pass

...d: 0 FastCopy.exe WriteFile \\10.19.250.98\Public\1GB.img Offset: 92,274,688, Length: 8,388,608, Priority: Normal I wonder if it has it's own SMB client code built in ? Either that or it knows what parameters to change in the SMB redirector to request 8MB IO. I wonder if setting a CreateOptions allows this somehow ?

...o users and the ones which we use for >>>>>> testing llvm itself. The options we want to expose should be just >>>>>> constructor arguments. With that distinction we should be able to just >>>>>> not use the options added by cl::OptionRegistry::CreateOption unless >>>>>> cl::ParseCommandLineOptions is called. WebKit like clients would just >>>>>> not call cl::ParseCommandLineOptions. Would that work? >>>>>> >>>>>> >>>>>> This is actually how some of our inte...

...9;s no > reason for the opt or the storage to be global. > > We frown upon the use of globals, otherwise LLVM would be littered with them > like many other C++ code bases. I don't think cl::opts should be special at > all in this respect. Note that the call cl::OptionRegistry::CreateOption<bool>(&ScalarizeLoadStore, "ScalarizeLoadStore", "scalarize-load-store", cl::Hidden, cl::init(false), cl::desc("Allow the scalarizer pass to scalarize loads and store")); ScalarizeLoadStore can actually be a member variable as long as caller guarant...

...age to be global. > > > > We frown upon the use of globals, otherwise LLVM would be littered with them > > like many other C++ code bases. I don't think cl::opts should be special at > > all in this respect. > > > Note that the call > > cl::OptionRegistry::CreateOption<bool>(&ScalarizeLoadStore, > "ScalarizeLoadStore", > "scalarize-load-store", cl::Hidden, cl::init(false), > cl::desc("Allow the scalarizer pass to scalarize loads and store")); > > ScalarizeLoadStore can actually be a member variable a...

...t; We frown upon the use of globals, otherwise LLVM would be littered with them > > > like many other C++ code bases. I don't think cl::opts should be special at > > > all in this respect. > > > > > > Note that the call > > > > cl::OptionRegistry::CreateOption<bool>(&ScalarizeLoadStore, > > "ScalarizeLoadStore", > > "scalarize-load-store", cl::Hidden, cl::init(false), > > cl::desc("Allow the scalarizer pass to scalarize loads and store")); > > > > ScalarizeLoadStore can actual...

..., otherwise LLVM would be littered with them > > > > like many other C++ code bases. I don't think cl::opts should be special at > > > > all in this respect. > > > > > > > > > Note that the call > > > > > > cl::OptionRegistry::CreateOption<bool>(&ScalarizeLoadStore, > > > "ScalarizeLoadStore", > > > "scalarize-load-store", cl::Hidden, cl::init(false), > > > cl::desc("Allow the scalarizer pass to scalarize loads and store")); > > > > > > Scal...

Gotta say, centos has been tough to install and get working. The anaconda installer makes large drive setups horridly tedious (especially if reinstalling a lot). Package selection seems a bit off... I did a virtualization package, no custom..did not install qemu, libvirt, and all attempts to do any virtualization failed due to non-installed packages. Then I decided to select all the