search for: apoc

...een fixed. Part of the problem was that it took 2 hours to get a commit > through to CVS last night and the nightly tester had already started by > that time. Something needs to be done about the late night high load > situation on zion (backups?) Hi Reid, The problem is that the disk on apoc (one of our machines) has been dying recently, and has finally totally died. It's not clear why the fate of zion (the machine with CVS and everything else on it) is tied to apoc, but it apparently definitely is. It is possible that it will take a while to get this resolved, but hopefully...

I forgot to remove some crud from the configure script and it caused some of the nightly testers to fail last night. The problem has already been fixed. Part of the problem was that it took 2 hours to get a commit through to CVS last night and the nightly tester had already started by that time. Something needs to be done about the late night high load situation on zion (backups?) Reid

I've been attempting to write my pass (which depends on DSA and pool allocation) against the SVN trunk of LLVM and the llvm-poolalloc project. However, I was thinking it might be better to use the latest stable releases of these codebases. I know that this is the 2.5 branch for LLVM, but are there any stable releases of pool allocation? If so, would there be any disadvantage to my

...alloc on hello.bc on my Linux machine, and it did not assert or segfault. I'm hoping to update my Linux source to the latest poolalloc source code later today to make sure newer code isn't the problem (although I tend to doubt that this will change my results). I can also try poolalloc on Apoc to see if it does anything different than on the newer Linux machines. -- John T. > --Patrick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmde...

Hi, I'm trying to run the pool allocation pass through opt, and I'm running into problems. It segfaults frequently; for example, it does this when the input is a simple Hello World program: [simmon12 at apoc testcases]$ opt -load /home/vadve/simmon12/llvm/llvm/projects/llvm-poolalloc/Debug/lib/libLLVMDataStructure.so -load /home/vadve/simmon12/llvm/llvm/projects/llvm-poolalloc/Debug/lib/poolalloc.so -poolalloc hello.bc > hello.pool 0 opt 0x08469ccb 1 libLLVMDataStructure....

...t; on my Linux machine, and it did not assert or segfault. I'm hoping to > update my Linux source to the latest poolalloc source code later today > to make sure newer code isn't the problem (although I tend to doubt that > this will change my results). I can also try poolalloc on Apoc to see > if it does anything different than on the newer Linux machines. > > -- John T. > > >> --Patrick >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> ht...

...It only works on x86 platforms though. On our research machines you can use it from /home/vadve/lattner/local/x86/bin/valgrind. Just run it like this: valgrind dis < post-process.o ... ==6220== Conditional jump or move depends on uninitialised value(s) ==6220== at 0x805D883: (within /mounts/apoc/disks/0/localhome/lattner/cvs/llvm/tools/Debug/dis) ==6220== by 0x807EF26: Constant::mutateReferences(Value*, Value*) (Constants.cpp:700) ==6220== by 0x80544DA: BytecodeParser::ResolveReferencesToValue(Value*, unsigned) (Reader.cpp:265) ==6220== by 0x804F7A6: BytecodeParser::ParseConstantP...

...gt; I'm trying to run the pool allocation pass through opt, and I'm running > into problems. It segfaults frequently; for example, it does this when > the input is a simple Hello World program: > Can you email me the bitcode file that is causing the problem? > [simmon12 at apoc testcases]$ opt -load > /home/vadve/simmon12/llvm/llvm/projects/llvm-poolalloc/Debug/lib/libLLVMDataStructure.so > -load > /home/vadve/simmon12/llvm/llvm/projects/llvm-poolalloc/Debug/lib/poolalloc.so > -poolalloc hello.bc > hello.pool > 0 opt 0x08469ccb...

...ing 2.5.1p1 without problem. I get this message from both a Solaris 2.7 (x86) machine and a Solaris 2.6 (SPARC) machine. >From the x86 machine, I get ssh dozer 51 f6 46 8d 9d 98 17 a6 b6 10 79 43 57 d2 30 f8 Disconnecting: Bad packet length 1375094413. >From the SPARC machine, I get ssh apoc 2c 15 98 83 67 46 9e 27 f3 d0 db 34 89 55 64 ac Disconnecting: Bad packet length 739612803. Below, I've put some of the debug info. I also just confirmed that this happens from a RedHat Linux machine running 2.5.2p2 as well, when trying to connect to the same HP-UX machines. I can't upg...