search for: pmdebug

...ed in and the PassManager attempts to run on the processed module. Then, I get the following: Program received signal SIGSEGV, Segmentation fault. 0xb7f16abf in __dynamic_cast () from /usr/lib/libstdc++.so.5 #0 0xb7ea9abf in __dynamic_cast () from /usr/lib/libstdc++.so.5 #1 0x0843f19d in llvm::PMDebug::PrintArgumentInformation (P=0x85e3b00) at /.../llvm/lib/VMCore/Pass.cpp:132 #2 0x0843f1fc in llvm::PMDebug::PrintArgumentInformation (P=0x85ca030) at /.../llvm/lib/VMCore/Pass.cpp:134 #3 0x0844e3b8 in llvm::PMDebug::PerformPassStartupStuff (P=0x85ca030) at PassManagerT.h:66 #4 0x08444146 in...

Hi Bram, On Wed, 2006-08-16 at 22:41 +0200, Bram Adams wrote: > Op 16-aug-06, om 18:59 heeft Reid Spencer het volgende geschreven: > Are there any workarounds (using other LLVM-tools) to link a native > library with LLVM-bytecode? Yes. The general approach is to use llvm-as, llvm-dis, opt and llvm-link to work with the bytecode. You can also use gccld and gccas to run some canned

Hi, Op 16-aug-06, om 18:59 heeft Reid Spencer het volgende geschreven: >> llvm-ld: warning: Supposed library 'SOME_OTHER_LIB' isn't a library. > > The -l option is used to link libraries into the resulting executable. > I'm hoping "SOME_OTHER_LIB" is not the actual name and you're just > paraphrasing the actual command line. Note that native

...empts to run on the processed module. Then, I get the following: > > Program received signal SIGSEGV, Segmentation fault. > 0xb7f16abf in __dynamic_cast () from /usr/lib/libstdc++.so.5 > > #0 0xb7ea9abf in __dynamic_cast () from /usr/lib/libstdc++.so.5 > #1 0x0843f19d in llvm::PMDebug::PrintArgumentInformation > (P=0x85e3b00) at /.../llvm/lib/VMCore/Pass.cpp:132 > #2 0x0843f1fc in llvm::PMDebug::PrintArgumentInformation > (P=0x85ca030) at /.../llvm/lib/VMCore/Pass.cpp:134 > #3 0x0844e3b8 in llvm::PMDebug::PerformPassStartupStuff (P=0x85ca030) > at PassManagerT.h...