similar to: [LLVMdev] llvmc doesn't recognise .a files

Without this patch, opt is never called for llvm-assembly (.ll) files when "-opt" is passed to llvmc: $ llvmc -clang -v test.ll llc -f -O2 test.ll -o /tmp/llvm_gvO2nK/test.s as /tmp/llvm_gvO2nK/test.s -o /tmp/llvm_gvO2nK/test.o llvm-ld -native -disable-internalize /tmp/llvm_gvO2nK/test.o -o a.out $ llvmc -clang -opt -v test.ll llc -f -O2 test.ll -o /tmp/llvm_2xiL86/test.s as

Without this patch, opt is never called for llvm-assembly (.ll) files when "-opt" is passed to llvmc: $ llvmc -clang -v test.ll llc -f -O2 test.ll -o /tmp/llvm_gvO2nK/test.s as /tmp/llvm_gvO2nK/test.s -o /tmp/llvm_gvO2nK/test.o llvm-ld -native -disable-internalize /tmp/llvm_gvO2nK/test.o -o a.out $ llvmc -clang -opt -v test.ll llc -f -O2 test.ll -o /tmp/llvm_2xiL86/test.s as

I am getting this error while using the command "llvmc -O3 -Wall hello.cpp" where hello.cpp is some cpp file on my machine. llvmc is the driver calling a bunch of tools like llvm-g++, opt, llc etc. I think the llvmc tool could not probably locate the llvm-g++ tool. I would like to know where should I specify the path to llvm-g++ for llvmc to find them. Also can someone give me the link

Hi, Is it intended that llvmc should search PATH for llc? For example, this means that llvmc 2.7 can invoke llc 2.8: % echo $PATH /home/jdenny/installs/llvm/2.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games % /home/jdenny/installs/llvm/2.7/bin/llvmc test.ll llc: Unknown command line argument '-f'. Try: 'llc -help' % strace -f

On Sun, 2006-08-13 at 21:18 +0200, Bram Adams wrote: > Hi, > > Apparently there are two bugs in tools/llvmc/c: This tool is, as yet, unfinished. > > /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item > /.../llvm/tools/llvmc/c:28: Error: Expecting a program name > /.../llvm/tools/llvmc/c had 2 errors. Terminating. > > The first error relates to

> BTW, Chris's Makefile changes broke llvmc yesterday (r75379). I'm > working on a fix. Hi Mikhail, Did you get a chance to fix this. I still get errors while building examples. i00202 at ubuntu:~/projects/llvm/tools/llvmc/example/mcc16$ make make[1]: Entering directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/plugins' make[2]: Entering directory

Thank you so much for your reply, Chris. If so, can I ask you two things more? First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc? llvm-gcc doesn't seem to be working for these -O options... Second, I'm still not sure about difference between *.s and *.ll. LLVM assembly *.s file can be made from llvm-gcc with -S option. Another

Greetings everybody! In my quest to attract more users to llvmc, I've added support for compilation via the Clang front-end (previously, only llvm-gcc was supported). This is enabled with the '-clang' switch; basically, you can now just alias 'ccc' to 'llvmc -clang' and get the same functionality. Examples: Compile via Clang: $ llvmc -clang test.c

Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's

I was using llvmc along with the -opt option to perform static analyzes in some of the commonly used programs like bzip2, gzip, grep etc. I found that when llvmc is used to link libraries (.a or .so files) using the -l option it passes the library files to the linker ( for me it was llvm-gcc itself) but changes the order in which it was given to llvmc. Eg: the command: " llvmc -o grep.o -v

Hi, I am trying to build my own llvmc plugin, but somehow, the llvm makefiles do not pick up the plugin in the llvmc/plugins directory anymore in a recent (r129445) svn checkout. According to the tutorial (http://llvm.org/docs/CompilerDriverTutorial.html): $ cd tools/llvmc $ cp -r example/Simple plugins/Simple $ make LLVMC_BASED_DRIVER_NAME=mygcc LLVMC_BUILTIN_PLUGINS=Simple does not build

Hi, Apparently there are two bugs in tools/llvmc/c: /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item /.../llvm/tools/llvmc/c:28: Error: Expecting a program name /.../llvm/tools/llvmc/c had 2 errors. Terminating. The first error relates to the following line(s): lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \ %llvmgccdir%/lib/gcc/%llvmgccarch% ... the other one to:

Hi, > According to the FAQ llvmc is considered experimental/unsupported. But > FWIW, here's an issue I found while trying to use it on 32 bit x86 systems. I am the primary maintainer of llvmc. First of all, thanks for your bug report. > tools/llvmc/plugins/Base/Base.td hardcodes the -relocation-model=pic > option into invocations of llc: This part was copied verbatim from the

Thank you so much for your reply, Chris. If so, can I ask you two things more? First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc? llvm-gcc doesn't seem to be working for these -O options... Second, I'm still not sure about difference between *.s and *.ll. LLVM assembly *.s file can be made from llvm-gcc -S. Another assembly *.ll file comes

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > >> Hi Mikhail, >> How do you build mcc16 executable? >> > > This should work: > > $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 > $ make > > I configure llvm into a separate directory from source. When I do the steps you mentioned in

According to the FAQ llvmc is considered experimental/unsupported. But FWIW, here's an issue I found while trying to use it on 32 bit x86 systems. tools/llvmc/plugins/Base/Base.td hardcodes the -relocation-model=pic option into invocations of llc: def llc : Tool< [(in_language "llvm-bitcode"), (out_language "assembler"), (output_suffix "s"), (cmd_line

Hello, guys. I've tried to use llvmc to test optimization options but wasn't successful. Would you mind telling me what's wrong with this? ------------------------------------------------------------- $ llvmc chc_03.c -O3 -o chc_03 terminate called after throwing an instance of 'std::string' llvmc((anonymous namespace)::PrintStackTrace()+0x15)[0x8086091]

Hi Mikhail, On Thu, 28 Oct 2010, Mikhail Glushenkov wrote: > Joel E. Denny <jdenny <at> etinternational.com> writes: > > Is it intended that llvmc should search PATH for llc? For example, this > > means that llvmc 2.7 can invoke llc 2.8: > > [...] > > This is fixed in 2.8+ - llvmc now searches the directory it resides in first. I just built r117553 from

Reid Spencer wrote: > On Thu, 2006-08-17 at 08:55 -0700, Scott Michel wrote: > >>Regarding llvmc there is one small problem: with the gcc 4.0 frontend, >>"-emit-llvm" needs to be added to all of the translator.command lines. >>Not entirely sure how to conditionalize that in the configuration files. > > > Hi Scott, > > What is needed is a

Hi Sanjiv, 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > Hi Mikhail, > How do you build mcc16 executable? This should work: $ cd $LLVM_DIR/tools/llvmc/examples/mcc16 $ make If you're building from some other dir, you'll need to update mcc16/Makefile, so it knows where Makefile.common is located. > There are so many confusing things there: driver, plugins,