similar to: [LLVMdev] etc/llvm/c contains unresolved specify %llvmcc1%

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:

On Aug 24, 2007, at 1:52 PM, Holger Schurig wrote: > Is llvmc meant for compilation? > I'm not sure what the status of llvmc is (is anyone working on it?), but I don't believe it was ready for real use or was finished. If you would like to work on it, patches are welcomed! Thanks, Tanya > $ llvmc -c a.c -o a.o > /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output

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

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program

Hi, Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >> variable by the llvmc configuration parser. > > Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around > line > 304. Also, they are recognized by the lexer. Its more likely that when > you configured LLVM

Babak, As its manual page (http://llvm.org/docs/CommandGuide/html/llvmc.html) states, llvmc is an experimental tool: llvmc is considered an experimental LLVM tool because it has these deficiencies: Poor configuration support The support for configuring new languages, etc. is weak. There are many command line configurations that cannot be achieved with the current

Hi, I am trying to compile glibc on Linux using llvm. I need to do this for a research project. The problem is that llvmc doesn't work, and I guess I have to set CC=llvmc to get the glic compiled. For some reason llvmc complains that it cannot find %llvmcc1%. I have this problem both on my Mac and my Linux system. Other tools that I have tested including llvm-gcc work without any

On Tue, 8 May 2007, Babak Salamat wrote: > Yes, I have built and installed llvm-gcc and "llvm-gcc --print-prog- > name=cc1" return the correct path for cc1, so I assume its path is > set correctly in the config files, but I haven't installed config > files separately. Do I need to do that? Is there any documentation > about it? I'd strongly suggest just building

Reid, Thank you for your quick reply. Yes, I have built and installed llvm-gcc and "llvm-gcc --print-prog- name=cc1" return the correct path for cc1, so I assume its path is set correctly in the config files, but I haven't installed config files separately. Do I need to do that? Is there any documentation about it? Thank you again, Babak On May 8, 2007, at 7:33 PM, Reid

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.

Bram Adams wrote: > Hi, > > Op 14-aug-06, om 09:29 heeft Reid Spencer het volgende geschreven: > >> >>> Apparently, %llvmgccdir% and %llvmcc1% are not recognized as a useful >>> variable by the llvmc configuration parser. >> >> >> Actually, they are. See tools/llvmc/ConfigurationDriver.cpp around line >> 304. Also, they are recognized

Thank you Chris. Actually, I have changed the stack organization in the "llc" source codes for x86 target. Thus, I need libraries compiled with the new stack organization. If I use llvm-gcc (and apparently also llvmc), llc will not be invoked. I was hoping that llvmc would call llvm-gcc to compile to bc file and then call llc to compile to native assembly, but apparently this

Reid and Bill, Thank you very much for your helpful comments. Your comments helped me find out what part of my work was wrong that my changes were not effective in llvm-gcc. Thank you again, Babak On May 9, 2007, at 1:57 PM, Reid Spencer wrote: > On Wed, 2007-05-09 at 13:38 -0700, Babak Salamat wrote: >> I am convinced to use llvm-gcc. As I mentioned in my previous email, >> I

On Wed, 2007-05-09 at 13:38 -0700, Babak Salamat wrote: > I am convinced to use llvm-gcc. As I mentioned in my previous email, > I have changed native code generation in llc to generate code with a > different stack organization. In order to have working binaries, the > libraries must be compiled with the new tool and have the same stack > organization. Now that I cannot use

I am convinced to use llvm-gcc. As I mentioned in my previous email, I have changed native code generation in llc to generate code with a different stack organization. In order to have working binaries, the libraries must be compiled with the new tool and have the same stack organization. Now that I cannot use llc, it seems that I have to modify llvm-gcc to have it generate code with the

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

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 >  

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 Sep 4, 2011, at 8:50 PM, Eli Friedman wrote: > 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 ::

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