similar to: [LLVMdev] linking a parser bitcode

Hello > It is complaining about not being able to find __gxx_personality_sj0 and the LLVM command line parser-related files.  What else do we need to link? This is personality function for sjlj eh. How the source bitcode files in questions were generated? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello Anton, Our main.bc was generated with the following command line: llvm-g++ -Illvm\include -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -c -emit-llvm -omain.bc main.cpp The amos.bc file was generated by our experimental llvm-peg parser generator whose internal workings are assembled internally using LLVM Assembly. The parser generator links a C++ library bitcode with C bindings called

Hello, Samuel > llvm-g++ -Illvm\include -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -c -emit-llvm -omain.bc main.cpp Ok. How was llvm-g++ built? Have you used release tarball, or built everything by hands? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello Anton, While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from. Does this mean that the LLVM libraries we're using are broken? Type.cpp ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x750):

Hello, Samuel > While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from.  Does this mean that the LLVM libraries we're using are broken? > > Type.cpp > ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' >

Hello Anton, We used the release tarball. Oh! I forgot to mention it's the version 2.5 stable release that we've been developing with. Thanks, --Sam ----- Original Message ---- > From: Anton Korobeynikov <anton at korobeynikov.info> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Fri,

Hello all, Does anyone have any inside why I can't get the below simple C API test to link? This is on a 32-bit Gentoo Linux system and LLVM TOT which was compiled with enable-optimized, gcc is 4.3.2. 15:26|melis at juggle2:~/c/llvmpy> cat t.c #include "llvm-c/Core.h" int main() { LLVMContextRef ctx; ctx = LLVMContextCreate(); return 0; } 15:29|melis at

Hello, Samuel > We used the release tarball.  Oh!  I forgot to mention it's the version 2.5 stable release that we've been developing with. Hrm, something is broken there.... Try to compile your code with -fno-exceptions then -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

I'm adding OProfile support to the JIT (patch at http://codereview.appspot.com/89041), and I'm running into trouble with getting llvm-config to print the right things to let external programs link. For some background, oprofile installs an agent library into <prefix>/lib/oprofile/libopagent.{a,so}. This isn't on the loader's default search path, even if <prefix>==/usr,

Howdy do LLVM folks! I've exhausted what I can do on my own to make a GC example bind (usual googling, reading, playing, looking at source). I can't find the shadow collector lib or perhaps the -l options needed to link my sample (not even to point where I'm figuring out GC actually as I can't link). Not sure this IR is correct but here is what I've been playing

On Oct 25, 2009, at 1:58 PM, Graham Wakefield wrote: > Hi all, > > (Sorry if the answer to this is obvious - and thanks in advance~) > > Short version: > linker error of _backtrace from LLVMSystem.a building a dynamic > library embedding LLVM/clang, both against the OSX 10.4 sdk. > > Long version: > I've just tried rebuilding my project using the 2.6 release,

hello, I'm attempting to build the inferno source tree using either of native LTO or jit'd bins and having no obvious luck. im using macports (current as of this email) llvm-2.5 and llvm-gcc on a macbook pro (x86) following the inferno directions verbatim will use 'cc' as the compiler and just works. the build tools are different from the naive build tools as follows:

Hi all, (Sorry if the answer to this is obvious - and thanks in advance~) Short version: linker error of _backtrace from LLVMSystem.a building a dynamic library embedding LLVM/clang, both against the OSX 10.4 sdk. Long version: I've just tried rebuilding my project using the 2.6 release, using the following commands to try and force LLVM to build against the OSX 10.4 sdk (I am

Hi, I'm having a hard time linking the LLVM/clang libraries in Xcode. I've been fighting this for a couple of days now, and decided to make a fresh checkout and a super-simple demo project to try and isolate the problem, but even so I'm getting undefined symbol errors in the linker for the static libraries LLVM is producing. This is really baffling, so probably I'm

>From CVS: llvm[3]: Compiling SJLJ-Exception.cpp for Debug build (bytecode) SJLJ-Exception.cpp:16:19: cstdlib: No such file or directory SJLJ-Exception.cpp:17:19: cassert: No such file or directory SJLJ-Exception.cpp: In function `void SJLJDestructor(llvm_exception*)': SJLJ-Exception.cpp:43: error: `free' undeclared (first use this function) SJLJ-Exception.cpp:43: error: (Each

Hi all, Well, suggestion for workarounds for the namespace problems are welcome... this is a 7 minutes compile files on a pentium 4 3ghz 700Mb ram... The fatal error at the end MAY depend on the previous... or at least, I hope so. cl /nologo /TP /EHsc /GR /Zi /Yd /D__STDC_LIMIT_MACROS /DHAVE__FINITE_IN_FLOAT_H /DHAVE__ISNAN_IN_FLOAT_H /ISTLport-4.6.2\stlport /Illvm\inc lude

Dear list, I want to add SJLJ exception handling to my frontend. Unfortunately, there doesn't seem to be any examples in the documentation as to how to use the intrinsics @llvm.eh.sjlj.setjmp @llvm.eh.sjlj.longjmp @llvm.eh.sjlj.lsda @llvm.eh.sjlj.callsite Is there a way to force Clang to use SJLJ exception handling for C++? That way I would be able to look at its output to learn how to use

Greetings, I'm trying to implement exception handling in my front end. I have a prototype working using the Itanium ABI on Linux x86_64, but I'm not sure how to proceed for other platforms. So I was wondering: which OS/architecture combinations support zero-cost EH, and which support SJLJ? My main concern is keeping the IR for call sites platform independent. Right now, it looks like to

Hi All, I am trying to make R package using R 2.6.2 And I am getting following error. When I give R CMD check t1\ ---------- Making package t1 ------------ adding build stamp to DESCRIPTION making DLL ... making CGHseg_rewrite.d from CGHseg_rewrite.c making rowMedians.d from rowMedians.c making runavg.d from runavg.c gcc-sjlj -std=gnu99 -Ic:/R/R-2.6.2/include -O3 -Wall -c

It seems that version of ICU_531 in <http://www.stats.ox.ac.uk/pub/Rtools/goodies/> as of June 25, 2014, was compiled using sjlj exception handling (current gcc-4.6.3, perhaps?). I say that as I am trying a 4.9.2 distribution which uses seh handling, and I get errors like: gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o editor.o embeddedR.o extra.o malloc.o