llvm dev - Jun 2006 - [LLVMdev] llvm-gcc 4.0 for Linux@x86

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 working just fine before, I don't know what I
did differently last time I compiled it.

- John

On 6/5/06, Rafael Espíndola <rafael.espindola at gmail.com>
wrote:
>
> 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
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>


-- 
John Trimble
Research Assistant
University of Arizona
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20060606/906ee394/attachment.html>

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 .s file instead of
native
  -emit-llvm-bc               Emit LLVM IR to the output file instead of
native

Please note that I was successful today in building llvm-gcc4 on Linux
(FC3) and there is now a binary version available for Linux at:

http://llvm.org/2006-06-01-llvm-gcc4-linux-x86-binary.tar.gz

Reid.

On Tue, 2006-06-06 at 19:17 -0700, John Trimble wrote:
> 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 working
> just fine before, I don't know what I did differently last time I
> compiled it.
> 
> - John
> 
> On 6/5/06, Rafael Espíndola <rafael.espindola at gmail.com> wrote:
>         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
>         _______________________________________________
>         LLVM Developers mailing list
>         LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>         http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> 
> 
> -- 
> John Trimble
> Research Assistant 
> University of Arizona 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20060606/95e4bec3/attachment.sig>