search for: module2

...sage; raw_string_ostream Stream(Message); DiagnosticPrinterRawOStream DP(Stream); LLVMBool Result; // 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...

...Stream(Message); > DiagnosticPrinterRawOStream DP(Stream); > LLVMBool Result; > // 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, "f...

...iving License certification. We are presently developing release 2.0 of the OpenICDL courseware http://icdl.tsf.org.za/devcourseware.html Module 2 is of particular interest to distros and desktops. The first version of module 2 was written for MDK. http://icdl.tsf.org.za/devcourses/mod2/mandrake/module2-all.html Since then we have received a contribution for RedHat/Fedora http://icdl.tsf.org.za/devcourses/mod2/redhat/module2-all.html Another for Ubuntu. If possible, we would like to extend the possibility to every distro to have a version of module 2 that they can call their own. Since the Red...

In rsyncd.conf I'd like to be able to specify something like: [module1] gateway 10.168.172.9 or (I think we have to change the protocol a little for this one): [module2] redirect datasource.my.domain I've run into this need a few times, and I think it might be useful enough to add (both of these) to the daemon configuration. I'm asking the list to see if either of these might be useful to someone else. I want to serve a large number of "content...

On 08/08/2013 11:04 AM, David Chisnall wrote: > What happens when I link together two IR modules from different front ends that have different language-specific address spaces? I agree with Micah: if during the linking two IR modules there are incoherences (e.g. in module1 2 -> 1 and in module2 2 -> 3) then the modules are incompatible and the link process should fail. > I would be very hesitant about using address spaces until we've fixed their semantics to disallow bitcasts between different address spaces and require an explicit address space cast. To illustrate the proble...

I have 2 xp100's and one TDM400P. I've plugged a phone into the tdm40b, and when i take it off hook sometimes i get a dialtone, other times i get the message "Power alarm of module2, resetting" spit out to the console from the wcfxs driver does anyone know what this could be? I've tried two different phones, with the same result on both. I changed the signalling to fxsls, and i had a dial tone on both phones, but the lines soon died with the power alarm message aga...

...sus on whether 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...

...(e.g. /tftpboot/linux-install/). without a path option, the modules need to use paths relative to the prefix, this can be inconvenient and clutter the command line. with this change it is possible to do: * kernel /zzz/zzzzzz/zzzzz/mboot.c32 * append -p /some/module/path kernel.gz --- module1.gz --- module2.gz instead of: * kernel /zzz/zzzzzz/zzzzz/mboot.c32 * append /some/module/path/kernel.gz --- /some/module/path/module1.gz --- /some/module/path/module2.gz signed-off-by: Damien Nozay <damien /dot nozay /at gmail.com> --- diff -u -r -X nodiff syslinux-3.82-orig/com32/mboot/mboot.c syslinux-3....

...virtual resources seems 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...

...ll wrote: > >> What happens when I link together two IR modules from different front >> ends that have different language-specific address spaces? >> > > I agree with Micah: if during the linking two IR modules there are > incoherences (e.g. in module1 2 -> 1 and in module2 2 -> 3) then the > modules are incompatible and the link process should fail. > > > I would be very hesitant about using address spaces until we've fixed >> their semantics to disallow bitcasts between different address spaces and >> require an explicit address space...

On 8 Aug 2013, at 04:23, Pete Cooper <peter_cooper at apple.com> wrote: > > On Aug 7, 2013, at 7:23 PM, Michele Scandale <michele.scandale at gmail.com> wrote: > >> On 08/08/2013 03:52 AM, Pete Cooper wrote: >> >> From here I understand that in the IR there are addrspace(N) where N=0,1,2,3,... according to the target independent mapping done by the

On Aug 7, 2013, at 7:23 PM, Michele Scandale <michele.scandale at gmail.com> wrote: > On 08/08/2013 03:52 AM, Pete Cooper wrote: >>> Why a backend should be responsible (meaning have knowledge) for a >>> mapping between high level address spaces and low level address spaces? >> Thats true. I’m thinking entirely from the persecutive of the backend >> doing