similar to: [LLVMdev] llvm-gcc 4.0 for Linux@x86

I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've tried and failed. The instructions in CFEBuildInstrs.html are for llvm-gcc3 and probably won't work as-is. Reid. On Sat, 2006-06-03 at 19:39 +0300, Yossi Kreinin wrote: > Hi! > > Apparently there are no precompiled binaries for llvm-gcc 4.0 for Linux. > > I've tried downloading the sources

On 6/3/06, Reid Spencer <reid at x10sys.com> wrote: > I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've > tried and failed. I have :-) There was some patches, but I believe that they were all merged in the latest snapshot. Rafael

Hmm, today I just tried compiling the llvm-gcc 4.0 frontend again on linux (Fedora Core 3 I believe) and I seem to be suddenly having the problem that Yossi Kreinin mentioned. The frontend seems to be using normal gcc to compile as I no longer get a bytecode file after compilation. When I pass the --version argument it claims to be the LLVM 4.0.1 frontend. Any ideas what might cause this? It was

Hi John, llvm-gcc4 by default emits object files, just as gcc does. This is by design. If you want to get bytecode output you need to use the --emit- llvm-bc option. A complete list of the options that llvm-gcc4 supports can be obtained with "llvm-gcc -v --help" (lots of output). Here are the descriptions of the --emit-llvm options: -emit-llvm Emit LLVM code to the

Hi! Apparently llvm-gcc ignores #line directives in source files when generating debug information. When I compile this: //test int f(int a) { #line 1 "someplace" return a*a; } //end with `llvm -g -S lines.c`, `someplace' is not mentioned in lines.s. It also looks like functions #included from header files get attributed to the #including file (albeit at the right line number).

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

Chris asked me to write up "LLVM Developer's Guide to Dwarf Support" for LLVM maintainers. We are still in early stages, but we thought we'd get it out there for the "need to bleeders." At some point this information will be formalized and added to the LLVM documentation. The enclosed document gives specific instructions for adding source line number support

Hi! The LLVM Bytecode File Format specifies an optional SectionID attribute for globals. I didn't find a matching attribute in the LLVM source code. Code such as: int a __attribute__ ((section ("A_SECTION"))); compiles with llvm-gcc, but apparently the section information is stripped (the object file doesn't contain "A_SECTION"). Is the SectionID feature

Hi! A (small) tar archive with files exposing an apparent LLVM optimizer bug is attached; I didn't find a way to attach files in the bugzilla interface. What's the best way to report bugs taking several files to reproduce? -- Yossi -------------- next part -------------- A non-text attachment was scrubbed... Name: bugreport.tgz Type: application/x-gtar Size: 2242 bytes Desc: not

Hi! I'm working on an LLVM back-end for a processor with a stack machine architecture. After experimenting with code generation directly from the LLVM representation, I'm studying the target-independant code generator. As far as I understand, there currently exists a target-independant infrastructure for legalization, instruction selection, scheduling and register allocation. It is clear

On Tue, 2007-16-01 at 02:50 +0000, Reid Spencer wrote: > > The build instructions provided tell me to build llvm-gcc first from > > the source. > > The source for that tells me to build llvm first from the source. I'm > > not sure where to go from this point. > You should build llvm first, then llvm-gcc. When I build LLVM first, however, I get told that it

Chris Lattner wrote: > > This looks like you're compiling llvm-gcc3, which is quite dead by now. > Please follow these instructions: > http://llvm.org/docs/CFEBuildInstrs.html > > Oups, sorry for that. Here is the error message with the latest svn version: gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic

> Well, it depends on the configure parameter used while building llvm- > gcc. Hmm, there are other pages on the the website that tell you how you should configure gcc, e.g. you're led from "How to build the C/C++ Frontend" at http://llvm.org/docs/CFEBuildInstrs.html to Subversion HEAD (by virtue of an "svn co"). Then you're supposed to look at README.LLVM. And

On Aug 24, 2007, at 1:45 PM, Holger Schurig wrote: > In the gray block below "Example of link time optimization" there are > some source files and then a list of commands to execute: > > $ llvm-gcc4 --emit-llvm -c a.c -o a.o > $ llvm-gcc4 -c main.c -o main.o > $ llvm-gcc4 a.o main.o -o main > > 1) in current LLVM (e.g. llvm itself, cfe, llvm-gcc-4.0) no binary

I am trying to compile the cfrontend for gcc3, not gcc4. I did ./configure --prefix=/opt/llvmgcc --enable-languages=c,c++ After adding the --enable-languages flag I get "xgcc: installation problem, cannot exec `gccas': No such file or directory" It is true, I don't have gccas in my PATH, nor does the file gccas appear in my cfrontend directory. Is my configuration wrong, yet

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

On Sat, 2006-06-03 at 11:25 -0700, Reid Spencer wrote: > I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've > tried and failed. I've successfully built and used llvm-gcc4 on linux/alpha Andrew

OK, seems like there were unused TARGET_MACHO macros that would protect these errors from happening. I made some modifications that add #if TARGET_MACHO. Now the error is a linkage problem: /home/varth/project/llvm-cvs/llvm-gcc4/obj/gcc/xgcc: symbol lookup error: /home/varth/project/llvm-cvs/llvm-gcc4/obj/gcc/libgcc_s.so.1: undefined symbol: __thenan_sf And even if I force the definition of

The web page "LLVM Link Time Optimization: Design and Implementation" contains errors. In the gray block below "Example of link time optimization" there are some source files and then a list of commands to execute: $ llvm-gcc4 --emit-llvm -c a.c -o a.o $ llvm-gcc4 -c main.c -o main.o $ llvm-gcc4 a.o main.o -o main 1) in current LLVM (e.g. llvm itself, cfe, llvm-gcc-4.0) no

Thank you, Reid, I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get gccld: warning: Cannot find library 'crtend' gccld: warning: Cannot find library 'c' I have the libraries in my llvm directory: llvm/runtime/GCCLibraries/crtend Well, how do I link this to the LLVM runtime stuff? Before building from the source, I had copied all the .h from my old gcc 4.0 to