similar to: [LLVMdev] Clang "warning: cannot find entry symbol mit-llvm-bc"

Hi, I want to know what benchmarks can LLVM compile and run successfully. Such as SPEC CPU2000, SPEC CPU2006 or other benchmarks. Thanks Shengmei -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091221/ed70efce/attachment.html>

[spark at oxygen llvm]$ llvmc -clang ~/a.c /home2/yjhuang/tools/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.4.2/../../../../x86_64-unknown-linux-gnu/bin/ld: warning: cannot find entry symbol mit-llvm-bc; defaulting to 00000000004003c0 llc: bitcode didn't read correctly. Reason: Bitcode stream should be a multiple of 4 bytes in length 出现error,加-v选项，发现是clang -x c -emit-llvm-bc /home2/spark/a.c -o

On Sun, Dec 20, 2009 at 7:06 PM, Li Shengmei <lism03 at gmail.com> wrote: > Hi, > >          I want to know what benchmarks can LLVM compile and run > successfully. > > Such as SPEC CPU2000, SPEC CPU2006 or other benchmarks. llvm-gcc can compile essentially anything in C/C++. -Eli

Hi, all We want to learn the IR of LLVM. Are there any information or documents you can suggest? Or any suggestions are welcome. Thanks Shengmei -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091211/0a788413/attachment.html>

Hi, all I use llvm-gcc -O4 to compile SPEC 2000, some benchmarks can't be built successfully, such as 164.gzip, 175.vpr etc. The error messages are as follows. .. zh.o unlzw.o unpack.o unzip.o util.o zip.o -o gzip bits.o: file not recognized: File format not recognized collect2: ld returned 1 exit status specmake: *** [gzip] Error 1 specmake options 2> options.err |

On 2009-12-23 08:22, Li Shengmei wrote: > > Hi, all > > I use llvm-gcc –O4 to compile SPEC 2000, some benchmarks > can’t be built successfully, such as 164.gzip, 175.vpr etc. > > The error messages are as follows. > > > > …… > > zh.o unlzw.o unpack.o unzip.o util.o zip.o -o gzip > > bits.o: file not recognized: File format not recognized

Hi, I built LLVM + Clang on Mac OS X and ran make check. I get the following result summary: Failing Tests (11): LLVM :: LLVMC/C++/dash-x.cpp LLVM :: LLVMC/C++/hello.cpp LLVM :: LLVMC/C++/just-compile.cpp LLVM :: LLVMC/C++/together.cpp LLVM :: LLVMC/C++/unknown_suffix.unk LLVM :: LLVMC/C/hello.c LLVM :: LLVMC/C/opt-test.c LLVM :: LLVMC/C/sink.c LLVM ::

On Sun, Sep 4, 2011 at 8:40 PM, S. Bharadwaj Yadavalli <bharadwajy at gmail.com> wrote: > Hi, > > I built LLVM + Clang on Mac OS X and ran make check. I get the > following result summary: > > Failing Tests (11): >    LLVM :: LLVMC/C++/dash-x.cpp >    LLVM :: LLVMC/C++/hello.cpp >    LLVM :: LLVMC/C++/just-compile.cpp >    LLVM :: LLVMC/C++/together.cpp >  

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

Hello, can i compile binary file .bc in my cpp program? now i use following code: if (system("opt a.out.bc -std-compile-opts -disable-inlining -loop-deletion -loop-extract -loop-extract-single -loop-rotate -loop-index-split -loop-unroll -opt-phis -loop-unswitch -loop-reduce -o test.bc") == -1) { Error("Don't install LLVM!"); exit(1); } if (system("llvmc test.bc -o

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:

I'm seeing this new build failure, starting some time yesterday on ARM: make[3]: Entering directory `/home/nlewycky/llvm/tools/llvmc/driver' llvm[3]: Linking Debug executable llvmc g++ -DLLVMC_BUILTIN_PLUGIN_1=Base -DLLVMC_BUILTIN_PLUGIN_2=Clang -I/home/nlewycky/llvm/include -I/home/nlewycky/llvm/tools/llvmc/driver -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g

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

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

On Oct 29, 2010, at 11:30 PM, Xinliang David Li wrote: > > > On Fri, Oct 29, 2010 at 11:14 PM, Chris Lattner <clattner at apple.com> wrote: > I strongly recommend not using llvmc unless you know exactly what you're doing and what the features and limitations of llvmc are. Please use the clang driver. > > Is llvmc just a wrapper on top of llvm-gcc and clang? In

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

Nick Lewycky wrote: > I'm seeing this new build failure, starting some time yesterday on ARM: > > make[3]: Entering directory `/home/nlewycky/llvm/tools/llvmc/driver' > llvm[3]: Linking Debug executable llvmc > g++ -DLLVMC_BUILTIN_PLUGIN_1=Base -DLLVMC_BUILTIN_PLUGIN_2=Clang -I/home/nlewycky/llvm/include -I/home/nlewycky/llvm/tools/llvmc/driver -D_DEBUG -D_GNU_SOURCE

On Fri, Oct 29, 2010 at 11:14 PM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 29, 2010, at 10:21 PM, Xinliang David Li wrote: > > > > 2010/10/29 Rafael Espíndola <rafael.espindola at gmail.com> > >> > clang -x c foo.c -emit-llvm-bc -o /tmp/llvm_JnS1o8/foo.bc >> > (.text+0x20): undefined reference to `main' >> > collect2:

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

Babak, I strongly suggest you drop trying to use llvmc. Instead, probably just compiling your library with llvm-gcc should be sufficient. The llvm-gcc tool has much of llc's functionality built in to it so you're going to get the same output. If that doesn't work for you, then please describe what you're trying to do in more detail and we'll tell you how it can be done.