similar to: [LLVMdev] Adding system libraries to the LLVM build

On Tue, 15 Mar 2005, Evan Jones wrote: > I'm back working on my threading patch for the LLVM JIT after being > distracted by a paper deadline. I think I have things working nicely on Mac > OS X (I just did a CVS up and it will take another hour or two to build), but > I'm having an issue with building on Linux. Specifically, "lli" fails to link > because it now

On Mar 16, 2005, at 12:01, Chris Lattner wrote: > It's not clear to me if pthreads will be required just by the > JIT-using-tools, or if it will be required by everything. If you have > thread-support stuff going into lib/Support, all llvm tools should be > linked to libpthread. Well, at the moment, I've added a mutex to ExecutionEngine. Thus, anything that pulls in this

Hi, I tried that out, I got a new error about pthreads in my config.log. Could you take another look. Thanks again, Reza > On Aug 20, 2019, at 12:36 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Tue, Aug 20, 2019 at 12:29:15PM -0400, reza shahriari wrote: >> Hi, >> >> I have attached my compressed config file. >> >> Thanks,

Thanks so much. I got it to go past pthreads. Now I am working on other dependencies > On Aug 20, 2019, at 1:30 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Tue, Aug 20, 2019 at 01:03:40PM -0400, reza shahriari wrote: >> Hi, >> >> I tried that out, I got a new error about pthreads in my config.log. > > It finds the header file now which is

All, I'm upgrading some code that uses LLVM from 3.6 to 3.7. It looks like the llvm::cl::parser subclasses are now final? We had been doing: struct MaxThreadsParser : public llvm::cl::parser<unsigned> { bool parse(llvm::cl::Option &O, llvm::StringRef ArgName, llvm::StringRef Arg, unsigned &Val); }; But that's now causing: In file included from

Hi LLVM'ers, I'm trying to build the DotGNU project with the LLVM-tools. After minor modifications of source and build code and some configure housekeeping, it seems that I've managed so far to build all the DotGNU tools. However, when extensively using the DotGNU tools I get this error message: make[1]: Entering directory `/home/hb/projects/build/LLVM/pnet-1-1/samples'

On Feb 8, 2005, at 21:36, Chris Lattner wrote: > That is correct. If you try to run threaded programs in the JIT, it > might run into problems if multiple functions need to JIT functions at > the same time. This should be very simple to deal with, we just > haven't had anyone take up the task yet. Only the JIT is affected > here, not the static code generator or C

This is what I was trying to do when I ran into the HowToUseJIT problem. I've made a first attempt at adding locking to the JIT. Unfortunately, since I do not really understand the structure of LLVM, I could have very easily screwed something up. I touched two classes, the JIT and the ExecutionEngine. I need some help from someone who is more familiar with the code to make sure that I

Heres a question for anyone awake at this hour, does icecast2 require libpthread? I'm trying to build it on a freebsd 4.3 box, and it wants to link against libpthread. If this is not required on the freebsd platform, then is it safe to just take out of the makefile? Thanks Mike -- <mystica@darktech.org> --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project

Hi,all I'm working on how to build a whole-program bitcode file for big projects with a general solution,and I met a problem I simplify it as this: llvm-gcc -c -emit-llvm test.c llvm-ld test.o -lpthread //here llvm-ld tells me that "Cannot find library pthread" then I do this: llvm-ld test.o lli -load=/usr/lib/libpthread.so a.out.bc //lli tells me the /usr/lib/libpthread.so

When I ran configure after updating, I get various errors. First: % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc checking for a BSD-compatible install... /usr/bin/install -c checking build system type... i386-unknown-freebsd5.2.1 checking host system type... i386-unknown-freebsd5.2.1 checking target system type... i386-unknown-freebsd5.2.1 test: Unknown: bad

Hi Nick: Thanks for pointing me to libffi. Recompile LLVM with libffi does solve the problem of printf. But it still has other problems: 1) sinf() returns 0 in the interpreter, but returns correct value in JIT (see hellosin.c) 2) calling pthread_create cause lli to crash in the interpreter mode, but no problem in JIT (see phello.c). My questions are: i) can I call any arbitrary external function

Xu Yang wrote: > Hi Nick: > > The first problem have been solved by calling llvm-ld: > > $ llvm-ld -o hellosin.llvm hellosin.bc -lm > $ lli -force-interpreter=true -load=/usr/lib/libm.so hellosin.llvm.bc > hello sin: 0.50 Only because the optimizer saw sin(constant) and folded it away. The entire program became 'print constant string'. There is certainly a bug

On Wed, 24 Dec 2003, yue wrote: > I try to run lli with "--load=/lib/libpthread.so", but it shows: > --------------------------------------------------- > [yue at RH9 test]$ ./pthread.ll > Error opening '/lib/libpthread.so.0': /lib/libpthread.so.0: symbol > _errno, version GLIBC_2.0 not defined in file libc.so.6 with link time > reference > -load request

On Thu, 2005-07-07 at 13:52 +0200, Henrik Bach wrote: > make[1]: Entering directory `/home/hb/projects/build/LLVM/pnet-1-1/samples' > ../ilasm/ilasm -o evenodd.exe > /home/hb/projects/src/pnet-1/pnet-0.7.0/samples/evenodd.il > ERROR: Program used external function 'pthread_once' which could not be > resolved! >

Hi Nick: The first problem have been solved by calling llvm-ld: $ llvm-ld -o hellosin.llvm hellosin.bc -lm $ lli -force-interpreter=true -load=/usr/lib/libm.so hellosin.llvm.bc hello sin: 0.50 The pthread problem remains after llvm-ld: $ lli -force-interpreter=true -load=/lib/libpthread.so.0 phello.llvm.bc 0 lli 0x08796bf8 Segmentation fault For those who are getting "invalid

Try llvmgcc pthread.c -o pthread.ll -pthread You have to link in the pthreads library, and I believe -pthread is all you need on a redhat 9 box. Kevin > -----Original Message----- > From: llvmdev-admin at cs.uiuc.edu [mailto:llvmdev-admin at cs.uiuc.edu] On > Behalf Of yue > Sent: Tuesday, December 23, 2003 11:43 PM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] pthread?

Nan Zhu <zhunansjtu at gmail.com> writes: > llvm-gcc -c -emit-llvm test.c > > llvm-ld test.o -lpthread //here llvm-ld tells me that "Cannot find library > pthread" $ llvm-gcc -c -emit-llvm test.c $ llvm-ld test.o -lpthread $ ./a.out Error opening '/usr/lib/libpthread.a': /usr/lib/libpthread.a: invalid ELF header -load request ignored. Hello world

On Sat, 2005-08-27 at 11:47 -0700, Reid Spencer wrote: > Alkis Evlogimenos wrote: > > It seems that these two classes are the same... Maybe they should be > > merged into 1 class? > > > I think you're looking at something old. MutexLocker doesn't exist any more. llvm/Support/ThreadSupport.h is not generated anymore? -- Alkis

On Tue, 8 Feb 2005, Evan Jones wrote: > On Feb 8, 2005, at 21:36, Chris Lattner wrote: >> That is correct. If you try to run threaded programs in the JIT, it might >> run into problems if multiple functions need to JIT functions at the same >> time. This should be very simple to deal with, we just haven't had anyone >> take up the task yet. Only the JIT is