search for: bigagli

Hi all, I have started the rsync in deamon mode. When I use the following command: rsync --port 9876 u018::treeA it seems to work fine but no files are copied from the server. Using rsync without the deamon works fine. I tried to debug it a little bit, but I am unable to figure out what's wrong. 337:david@u050 /export/treeA> rsync -r -vvv --port 9876 u018::treeA opening tcp

...the JIT memory manager to extend external symbol resolution if you like. In any event, calling functions in the current process should work just as you’ve seen it. > > -Andy > > > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Andrea Bigagli > Sent: Sunday, April 15, 2012 8:22 AM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] Proper way to use "host application" function from JIT code > > Hi, > I found myself doing very similar things to what's discussed in http://lists.cs.uiuc.edu/pipermail/cfe-dev...

Hi, the subject says it all... After some experimenting, I got a bit confused as far as what the proper thing to do might be.... I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese) where I also have successfully built a fsf-gcc 4.6.2 (and lately a 4.7 for that matter) from sources. Now, I think I understand that by playing

...ur own implementation of the JIT memory manager to extend external symbol resolution if you like. In any event, calling functions in the current process should work just as you've seen it. -Andy From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Andrea Bigagli Sent: Sunday, April 15, 2012 8:22 AM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Proper way to use "host application" function from JIT code Hi, I found myself doing very similar things to what's discussed in http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-July/009836.html. More p...

Hi, I found myself doing very similar things to what's discussed in http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-July/009836.html. More precisely, I've modified the clang-interpreter example so that I can specify a .cpp source file at runtime which is JIT-compiled and some functions inside it get called by the interpreter executable itself. In this context, "host-application"

...s __c11_atomic_* and it builds cleanly from what i've tested. I presently don't have a 10.7 box to test against trunk, but those errors are now gone from Linux. The thread to read: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-April/020686.html - Marc On 04/12/2012 10:44 AM, Andrea Bigagli wrote: > Hi, > the subject says it all... > > After some experimenting, I got a bit confused as far as what the > proper thing to do might be.... > > I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. > x86_64-apple-darwin11.3.0 to speak GNU's platform-ese)...

Hi, I'm really a novice in experimenting with LLVM, so I might be doing something plain wrong here, but I can't understand why this snippet // File ticket.cpp struct ticket { int field1; char field2[10]; } _ticket; goes fine through the sequence 1) clang++ -O0 -S -emit-llvm ticket.cpp (which generates ticket.s) 2) llc -march=cpp ticket.s So that I end up with a ticket.s.cpp that I