similar to: [LLVMdev] bc file only with llvm-gcc3?

On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach <michael_reichenbach at freenet.de> wrote: > question about: > http://llvm.org/docs/FAQ.html#translatec++ > "With llvm-gcc3, this will generate program and program.bc." > > Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? Those instructions are out of date; the current version of llvm-gcc

Dale Johannesen schrieb: > On Sep 17, 2008, at 2:36 PMPDT, Michael Reichenbach wrote: >> No matter if I try " >> llvm-g++ a.cpp -c -emit-llvm >> " with "LLVM-GCC 4.2 Front End Binaries for Mingw32/x86" on Windows XP >> or if I am trying it on Ubuntu... >> >> Only the a.o file will be created without any error messages. The .bc >>

Hello Michael, If you're just trying to run the code you can skip the llc and gcc states and go directly to lli. PowerPC and Intel x86 are the only architectures supported by the jit compiler right now but it should work fine from Windows. The C output backend needs some work since C isn't a low-level language enough to compile the abstractions of LLVM Assembly code. --Sam Crow --- On

Eli Friedman schrieb: > On Wed, Sep 17, 2008 at 1:31 PM, Michael Reichenbach > <michael_reichenbach at freenet.de> wrote: >> question about: >> http://llvm.org/docs/FAQ.html#translatec++ >> "With llvm-gcc3, this will generate program and program.bc." >> >> Is this llvm-gcc3 only out of date of is it really only llvm-gcc3? > > Those

On Wed, Sep 17, 2008 at 3:39 PM, Michael Reichenbach <michael_reichenbach at freenet.de> wrote: > program.c will contain some non-human generated code. But it doesn't > compile with gcc. There is an error, gcc complaints about undefined > reference to std::cout and such (the code was just a very small example > with cout). > > It hasn't be converted into "C

Eli Friedman schrieb: > On Wed, Sep 17, 2008 at 3:39 PM, Michael Reichenbach > <michael_reichenbach at freenet.de> wrote: >> program.c will contain some non-human generated code. But it doesn't >> compile with gcc. There is an error, gcc complaints about undefined >> reference to std::cout and such (the code was just a very small example >> with cout).

Hi! question about: http://llvm.org/docs/GettingStartedVS.html#tutorial "Note: while you cannot do this step on Windows, you can do it on a Unix system and transfer hello.bc to Windows. Important: transfer as a binary file!" Is this feature also planed for Windows? Regards, -mr

On Sep 17, 2008, at 2:36 PMPDT, Michael Reichenbach wrote: > > No matter if I try " > llvm-g++ a.cpp -c -emit-llvm > " with "LLVM-GCC 4.2 Front End Binaries for Mingw32/x86" on Windows XP > or if I am trying it on Ubuntu... > > Only the a.o file will be created without any error messages. The .bc > file will not be created, do you know why? -emit-llvm

Hi It would be pretty useful to have syslinux in linux kernel format so it can be chainloaded easy and directly by other bootloaders such as grub4dos. related topics: http://www.boot-land.net/forums/index.php?showtopic=7013 http://www.boot-land.net/forums/index.php?s=&showtopic=6119&view=findpost&p=59236

On Sunday 28 July 2002 02:06 am, you wrote: > On Sunday 28 July 2002 01:30 am, you wrote: > > Whenever I try to run it (ices)I get errors: > > > > cadmium:/work/dl/Audio/streaming/ices-0.2.3 # /usr/local/icecast/bin/ices > > --help /usr/local/icecast/bin/ices: error while loading shared libraries: > > libgcc_s.so.1: cannot open shared object file: No such file or

Hi Hendrik, On Mon, 2006-08-07 at 14:35 -0400, Hendrik Boom wrote: > I just downloaded the CVS version of llvm and llvm-test. Presumably > this is the one that's scheduled to become 1.8 in a few days. Not really. The current CVS head is quite a ways past release 1.8 at this point. If you want to get the release 1.8 preview, please check out the release_18 branch: cvs co -rrelease_18

Hi, I'm trying to compile some apps with the new llvm-gcc4 on amd64 linux to .bc files, rather than to the native code. The same process I used to build those apps before with llvm-gcc3 doesn't work: 1) export CC=llvm-gcc CXX=llvm-g++ CFLAGS="-g -fno-inline" CXXFLAGS="-g -fno-inline" 2) cd <whatever-app>; ./configure 3) make CFLAGS+=-emit-llvm

Unless I'm missing something, the problem lies directly with the fact that you are trying to do a link-stage operation with the GCC frontend. GCC, by default, probably runs "ld" or another system linker, which grabs the executable from binutils. This linker hasn't been modified (yet) to include support for .bc files, but you're compiler is emitting byte code to the *.o files.

Chandler/Domagoj, On Sun, 2006-12-10 at 10:53 -0500, Chandler Carruth wrote: > Unless I'm missing something, the problem lies directly with the fact > that you are trying to do a link-stage operation with the GCC > frontend. GCC, by default, probably runs "ld" or another system > linker, which grabs the executable from binutils. This linker hasn't > been modified

> I was only using the C++ standard lib. It doesn't need to be linked > because it's only a header. Better said, it can't be linked with the std > lib, never heard that it's needed to link it. Your program does need to have libstdc++ to linked it. > Btw the code compiles and runs for sure with a g++ and also with llvm-g++. Right, because they provide all needed extra

LLVMers, This doesn't affect release 1.X users, only those using the LLVM current (CVS head) version. With recent changes, the current version of LLVM will no longer read old assembly or bytecode files. The upgrade path from 1.X to 2.0 is now provided by the new llvm-upgrade tool. See: http://llvm.org/docs/CommandGuide/html/llvm-upgrade.html for details on how to use this command.

I just downloaded the CVS version of llvm and llvm-test. Presumably this is the one that's scheduled to become 1.8 in a few days. (1) To install llvm, do I really need the llvm version of the gcc front end? I have no special interest in yet another c/c++ conmpiler. (2) If I need llvm gcc, will the binary version suffice, or do I need to compile the CVS version? (3) If I need its source

On Fri, 2006-11-17 at 11:43 -0800, Chris Lattner wrote: > On Fri, 17 Nov 2006, John Criswell wrote: > > I don't think you will need to deal with any names. The C++ standard > > library has already been compiled to LLVM bytecode (it is part of the > > llvm-gcc/llvm-g++ distribution). If you use "llvm-g++ -lstdc++" it > > should link in whatever libstdc++

On Fri, 17 Nov 2006, John Criswell wrote: > I don't think you will need to deal with any names. The C++ standard > library has already been compiled to LLVM bytecode (it is part of the > llvm-gcc/llvm-g++ distribution). If you use "llvm-g++ -lstdc++" it > should link in whatever libstdc++ functions are needed by your program; > they will get translated to C code

On Mon, 07 Aug 2006 11:45:04 -0700, Reid Spencer wrote: > Hi Hendrik, > > On Mon, 2006-08-07 at 14:35 -0400, Hendrik Boom wrote: >> I just downloaded the CVS version of llvm and llvm-test. Presumably >> this is the one that's scheduled to become 1.8 in a few days. > > Not really. The current CVS head is quite a ways past release 1.8 at > this point. If you