search for: module3

Displaying 4 results from an estimated 4 matches for "module3".

Did you mean: module
2015 May 30
2
[LLVMdev] Linking modules across contexts crashes
...esult; // create blank modules and contexts LLVMContext *ctx1 = new LLVMContext; Module* module1 = new Module("module1", *ctx1); LLVMContext *ctx2 = new LLVMContext; Module* module2 = new Module("module2", *ctx2); LLVMContext *ctx3 = new LLVMContext; Module* module3 = new Module("module3", *ctx3); // fill modules llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx1), false), llvm::Function::ExternalLinkage, "f1", module1); llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx2), false), llvm::Function::E...
2015 Jun 01
2
[LLVMdev] Linking modules across contexts crashes
...k modules and contexts > LLVMContext *ctx1 = new LLVMContext; > Module* module1 = new Module("module1", *ctx1); > LLVMContext *ctx2 = new LLVMContext; > Module* module2 = new Module("module2", *ctx2); > LLVMContext *ctx3 = new LLVMContext; > Module* module3 = new Module("module3", *ctx3); > // fill modules > llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx1), false), llvm::Function::ExternalLinkage, "f1", module1); > llvm::Function::Create(llvm::FunctionType::get(Type::getInt32Ty(*ctx2), false), llvm:...
2004 Jan 27
1
"file has vanished" bug [rsync-HEAD-20040127-1010GMT]
...hether using multiple source modules when pulling from an rsync daemon is going to be ok? I recall some discussion on escaping spaces or quoting them in the past but I'm not sure if anything was decided. What I'm referring to is this case: rsync -av rsync://server/'module1 module2 module3' dest/ Right now the latest CVS still supports this. Thanks, -- Alberto --------------------------------- #!/bin/sh [ -d target ] && /bin/rm -rf target if [ ! -d one ] ; then mkdir one touch one/foo touch one/zoo fi if [ ! -d two ] ; then mkdir two touch...
2011 Aug 01
3
Class inheritance or virtual resources to manage apache modules
...ms to be the correct way to do this kind of thing. I however have had troubles with doing that and have ultimately ended up with the following using inheritance: class apache2::modules { # list apache modules to enable $enable_apachemods = [ "module1", "module2", "module3", ] # list apache modules to disable, basically all modules would be listed here by default $disable_apachemods = [ "module4", "module5", "module6", ] # Process list of apache modules to enable a2mod { $enable_apachemods: ensure => "present&q...