search for: premain

...om 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 file I get an infinite loop reporting the following: rdsuvideodrome:~/ciEx> ./ciEx.out Result = 55 <premain>: CommandLine Error: Argument 'verify-loop-info' defined more than once! <premain>: CommandLine Error: Argument 'verify-scev' defined more than once! <premain>: CommandLine Error: Argument 'scalar-evolution-max-iterations' defined more than once! <premain&g...

...he class is named SIL. I have setup AnalysisUsage object of SIL by doing the below: AU.setPreservesAll(); AU.addRequired<*ReachingDef*>(); AU.addRequired<*some other pass*>(); When I load the pass iel, I get the following error: 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 symbol: _ZTI11ReachingDef -load requ...

...;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! ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! It seems like the constructor for this argument is being run twice. ellsif works as expected, but I'd like to figure out what'...

...ith a loop I was using to find out the index of an Argument. It relied on the fact that getPrev() would eventually give 0, which worked in previous LLVM versions. 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: CommandLine Error: Argument 'debug' defined more than once! These are the arguments I provide to llvmc (I need the -disable-opt as some of the standard passes absolutely need to occur before my passes, and...

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 symbol:...

...river) 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! > ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! I recently had a similar problem when I wrote a new pass and built it into opt. This error message is confusing because the code t...

...hich > worked in previous LLVM versions. Ah, these should be private. Thanks for pointing this out, I'll fix ;-). You should use iterators. > 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: CommandLine Error: Argument 'debug' defined more than once! No idea. :) llvmc is a work in progress which has stagnated somewhat. I strongly recommend using llvm-gcc directly. -Chris -- http://nondot...

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: CommandLine Error: Argument 'debug' defined more than once! > >No idea. :) > >llvmc is a work in progress which has stagnated somewhat. I strongly >recommend using llvm-gcc directly. B...

...o 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 problem was given by the driver llvmc. It gives me following error: $ llvmc -O2 a.c -o a.o <premain>: CommandLine Error: Argument 'debug' defined more than once! llvmc: CommandLine Error: Argument 'debug' defined more than once! ../install/etc/llvm/c:55: Error: Expecting output type value ..install/etc/llvm/c had 1 errors. Terminating. Any ideas as why did I get this error? T...

...vmother.so /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../i686-pc-linux-gnu/bin/ld: warning: creating a DT_TEXTREL in object. In this configuration the libraries and tools work, except that the tools produce some error output before doing their job: $ ./compiler/llvm/tools/llc/llc --version <premain>: CommandLine Error: Argument 'inline-threshold' defined more than once! llc: CommandLine Error: Argument 'inline-threshold' defined more than once! Low Level Virtual Machine (http://llvm.org/): llvm version 2.3 DEBUG build with assertions. Can anyone help me fix these issue...

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

...s 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! >> ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! > > I recently had a similar problem when I wrote a new pass and built it into > opt. This error message is conf...

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

...; sample3.tst cmp sample1.bz2 sample1.rb2 cmp sample2.bz2 sample2.rb2 cmp sample3.bz2 sample3.rb2 cmp sample1.tst sample1.ref cmp sample2.tst sample2.ref cmp sample3.tst sample3.ref fi At the -O0 optimization level, it works just fine: ~/bzip2-1.0.4] main% ./ellsamake ellsif:<premain>: CommandLine Error: Argument 'machine-licm' defined more than once! ellsif: CommandLine Error: Argument 'machine-licm' defined more than once! adding bzip2.c as a C file adding crctable.c as a C file adding randtable.c as a C file adding compress.c as a C file ad...