similar to: [LLVMdev] Undefined symbol when loading pass

On Apr 5, 2010, at 7:10 PM, funceval wrote: > opt -load ../../../Release/lib/iel.so > <premain>: CommandLine Error: Argument 'inline-threshold' defined > more than once! > opt: CommandLine Error: Argument 'inline-threshold' defined more > than once! > Error opening '../../../Release/lib/iel.so': ../../../Release/lib/ > iel.so: undefined

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once!

Hi, Op 19-mei-07, om 00:39 heeft Chris Lattner het volgende geschreven: > Anton is right. You should be able to use -fno-builtins to disable > this. Thanks, that did the trick. Some final remarks (my app works again :-)): * llvm.va_start and similar intrinsics now have an i8* arg instead of an sbyte** * For some reason the Arguments of a Function are now circularly linked,

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument

Using the command: llvm-gcc -m64 hello.c resulted in the following error: sorry, unimplemented: 64-bit mode not compiled in Bill Wendling wrote: > > Did you compile it with -m64? > > -bw > > On Jul 24, 2009, at 11:00 PM, funceval wrote: > >> >> Hi, >> >> I just installed llvm on a 64 bit system and tried running it on a >> hello >>

On Sun, 20 May 2007, Bram Adams wrote: > Op 19-mei-07, om 00:39 heeft Chris Lattner het volgende geschreven: >> Anton is right. You should be able to use -fno-builtins to disable >> this. > > Thanks, that did the trick. > > Some final remarks (my app works again :-)): > * llvm.va_start and similar intrinsics now have an i8* arg instead > of an sbyte** ok >

On Tue, 22 May 2007 23:52:46 -0700 (PDT) Chris Lattner <sabre at nondot.org> wrote: >On Sun, 20 May 2007, Bram Adams wrote: >> On a related note: while using llvmc I have some test cases where the >> following error now pops up on Linux X86 (not on OSX): >> >> <premain>: CommandLine Error: Argument 'debug' defined more than once! >> llvmc:

Hello, This error message means that you haven't compiled LLVM-GCC from the source for your architecture. The distribution you have is probably for 32-bit machines only. Tell us more about your system configuration and maybe we can figure out where the problem arises in the compilation of LLVM-GCC. ----- Original Message ---- > From: funceval <funceval at gmail.com> > To:

Hi, I'm not sure if this is a libclang, llvm::cl or clang-interpreter issue so I'll try posting here for a response. I am using libclang as a frontend to the LLVM JIT (3.3 release). I started from the clang-interpreter example and have everything working (given a C/C++ source file I can have it JIT'd to memory and executed) for a single run. When I try to compile a second source

Hi, I just installed llvm on a 64 bit system and tried running it on a hello world program but I got the following errors: /tmp/ccXb6nzp.s: Assembler messages: /tmp/ccXb6nzp.s:9: Error: suffix or operands invalid for `push' /tmp/ccXb6nzp.s:21: Error: suffix or operands invalid for `pop' I have installed llvm 2.5 and it was configured with llvm-gcc4.2-2.5 Please help me resolve this

Did you compile it with -m64? -bw On Jul 24, 2009, at 11:00 PM, funceval wrote: > > Hi, > > I just installed llvm on a 64 bit system and tried running it on a > hello > world program but I got the following errors: > > /tmp/ccXb6nzp.s: Assembler messages: > /tmp/ccXb6nzp.s:9: Error: suffix or operands invalid for `push' > /tmp/ccXb6nzp.s:21: Error: suffix or

Hi, I'm starting to see more and more duplicates in my cur directory. they seem to be a copy of an incoming mail (messages share the same date) but they appears in the client as a message without subject and without sender or body. Their filename starts with an underscore and the 4th letter is a %. The rest of the filename is random (but it also includes my hostname). Which program could

Hi, I have written a pass to find the control dependences. Right now I am using a map of of basic blocks to vectors of basic blocks to store the dependences, so the dependence is represented in terms of basic blocks. Before I submit the patch for review, I wanted to know the format in which control dependences should be stored. 1) Should the dependence information be instead represented in terms

https://bugzilla.samba.org/show_bug.cgi?id=12029 Bug ID: 12029 Summary: Makefile missing dep gives parallel race for rounding.h Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee: wayned at

Today was the first day when I heard and read about llvm, and I would say I am pretty excited to learn about it. The design looks simply amazing and the codebase seems to be easy to follow. Way to go guys!!! I immediately downloaded and built the llvm-gcc front-end and the llvm tools and libs. Also, I could successfully use the llvm-gcc, llvm-dis and llc tools to see things in action. The only

For my language front-end I'm using a version of LLVM (2.3) that I have modified to compile with CMake. But it doesn't work as supposed to. A little background. I have split the files from "lib/" into four libraries: 1) llvmsystem: contains the files from "System/" 2) llvmsupport: contains the files from "Support/" 3) llvmcore: contains the files from

On Sat, 19 May 2007, Anton Korobeynikov wrote: >> * It seems that a C-call like printf("---\n") is transformed to puts >> ("---") in the LLVM IR instead of keeping it a printf. What are the >> circumstances in which this happens? Do other similar conversions >> occur? Can this be turned off (lower optimisation level?)? Manually >> replacing the

Jay Foad wrote: >> I'm linking a program (my ellsif driver) that basically brings in most >> of the LLVM stuff: bitcode reading, optimizations, linking, and target >> code generation. >> >> All of a sudden, I'm getting the following when I run: >> [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions >> -O5 >>

Hello, Bram > * It seems that a C-call like printf("---\n") is transformed to puts > ("---") in the LLVM IR instead of keeping it a printf. What are the > circumstances in which this happens? Do other similar conversions > occur? Can this be turned off (lower optimisation level?)? Manually > replacing the puts-calls by a printf-call is not

Hi, I've restarted my Elsa/LLVM project after three months of having real life intrude. I upgraded my LLVM source to the current trunk. I had to make a few changes to my source, e.g. LLVMFoldingBuilder became IRBuilder and several instances of "new" became "Create". Now, a test case that previously succeeded fails. I run the following script: #!/bin/sh if [ 1 -ne 0 ]