search for: annat

...utput though. Any suggestion on how to fit a glm with no intercept? Regards, Gudrun -- Gudrun Jonasdottir, M.Sc. Matematiska institutionen Stockholms Universitet SE- 106 91 Stockholm Work: +46 (0)8 16 45 56 Mobile: +46 (0)709 779 800 -------------------------------------------- "N?r inget annat hj?lper, l?s instruktionsboken." - Canns axiom

...>>> information ala DWARF. >> This isn't something you can do, this is far more tricky than you make >> it out to be. :) > Hehe, I know. Certainly if someone like you says that. But *if* the > front end is aware of the annotation, which would be doable, and the > annations are serializable in bytecode, then one would have this > information during LLVM bytecode processing as well. Yes. However, there would be no way to keep isomorphic LLVM types separate. This dramatically limits the usefulness of what you're trying to do. > One could also emit th...

...64e000 Deferred libpthread.so.0 ELF f764e000-f7792000 Dwarf libwine.so.1 ELF f7793000-f77b3000 Deferred ld-linux.so.2 ELF f77b3000-f77b4000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 00000008 (D) Z:\mnt\Annat\Spel\Mount&Blade With Fire and Sword\mb_wfas.exe 00000009 0 <== 0000000e services.exe 0000001b 0 00000017 0 00000015 0 00000014 0 00000010 0 0000000f 0 00000011 winedevice.exe 00000016 0 00000013...

Hi, I'm trying to setup automatic sync of files over SSH from node2 to node1. node2 is the "server" and node1 is the "client". I have setup rsync like this on the nodes which runs AIX (4.3.3 and 5.1): 1. Installed rsync from Linux Toolbox (rsync-2.5.4-1.aix4.3.ppc.rpm) on both nodes. 2. Added following to both nodes /etc/services file: rsync 873/tcp 3. Added

...ured debug >> information ala DWARF. > > > This isn't something you can do, this is far more tricky than you make > it out to be. :) > Hehe, I know. Certainly if someone like you says that. But *if* the front end is aware of the annotation, which would be doable, and the annations are serializable in bytecode, then one would have this information during LLVM bytecode processing as well. One could also emit the symbolic information like Relocation informations in a .section or as I am currently working with the JIT - use the JITs information about the annotations to get t...

On Fri, 24 Feb 2006, Jakob Praher wrote: > out of a matter of fact I am still using llvm version 1.5. I don't know > how 1.6 works in this matter. ok. > When translating a complex c application to llvm bytecodes, some > semantics are lost: > > Take for isntance the interesting attribute to put a variable in the > thread local data section (.tdata), this would be

hi all, out of a matter of fact I am still using llvm version 1.5. I don't know how 1.6 works in this matter. When translating a complex c application to llvm bytecodes, some semantics are lost: Take for isntance the interesting attribute to put a variable in the thread local data section (.tdata), this would be interesting to have in llvm. like in GCC you write: int x