Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html"
2007 Aug 24
0
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
On Aug 24, 2007, at 1:45 PM, Holger Schurig wrote:
> $ llvm-gcc --emit-llvm -c a.c -o a.o
> $ llvm-gcc -c main.c -o main.o
> $ llvm-gcc a.o main.o -o main
> a.o: file not recognized: File format not recognized
> collect2: ld returned 1 exit status
>
> Okay, that did not really work :-/
This document describes interface between llvm and linker. You need
system linker that
2007 Aug 24
0
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
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
2007 Aug 24
1
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
> 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
2007 Aug 24
1
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
> > $ llvm-gcc --emit-llvm -c a.c -o a.o
> > $ llvm-gcc -c main.c -o main.o
> > $ llvm-gcc a.o main.o -o main
> > a.o: file not recognized: File format not recognized
> > collect2: ld returned 1 exit status
> >
> > Okay, that did not really work :-/
>
> This document describes interface between llvm and linker. You need
> system linker that
2007 Aug 24
0
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
> 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 with
> the name "llvm-gcc4" get's
2007 Aug 24
1
[LLVMdev] Documentation error in http://llvm.org/docs/LinkTimeOptimization.html
> The documentation could be updated to say llvm-gcc
> but unless you specify the prefix "llvm-" during configure, it wont be
> named that either :)
llvm-top did this for you, see the "--program-prefix=llvm-" in
http://llvm.org/svn/llvm-project/llvm-gcc-4.0/trunk/build-for-llvm-top.sh
(I know that llvm-top hasn't even been announced, but at least when
Reid
2006 Aug 17
2
[LLVMdev] help with link problems
First, thanks to those who have responded to my earlier pleas for
help. You have either directly or indirectly helped me find the
answers I needed. I'm slowly getting up to speed with LLVM. Now I
have 2 more questions.
1) I'm using LLVM 1.8a with llvm-gcc3. I'm trying to compile firefox
(with regular gcc and make) while using LLVM to automatically
instrument one source file
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<b>Reid,<br>
<br>
I followed the steps but got stuck as described
2006 Nov 06
0
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=utf-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Reid,<br>
<br>
Here's the backtrace you asked for:<br>
<br>
2006 Dec 03
3
[LLVMdev] problem building gcc4 front end on fedora core 5
I'm getting a build error when trying to build gcc4 from sources. This is
for the recent 1.9 release.
How I built llvm-1.9:
-----------------------------
tar zxf llvm-1.9.tar.gz
cd llvm-1.9/
./configure --prefix=/custom/llvm-1.9
make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only
make install
How I built gcc4:
-----------------------------
export
2007 Feb 28
1
[LLVMdev] Cygwin release build error
I did not realize that '--enable-llvm' was required and that invalidates my debug build results which were built just with LLVM on the path.
I am now getting a segmentation fault when doing a 'make install' on LLVM-GCC4, possibly validating my original thoughts that GCC 4.1.1 was required to build LLVM-GCC 4.0.1. I will try using GCC 4.1.1.
Heres the error anyway :-
make[2]:
2006 Nov 06
2
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
Hi Robert,
On Mon, 2006-11-06 at 12:45 -0800, Robert Mykland wrote:
> Reid,
>
> Here's the backtrace you asked for:
>
> (gdb) bt
> #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction ()
Hmm, this is a little strange. Your LLVM build is non-debug (there's no
line numbers or arguments in any of the llvm related calls). However,
your llvm-gcc build seems to have
2006 Nov 06
4
[LLVMdev] Problems building cfrontend 4 source on SUSE 10.1
This is an libpath problem. When xgcc runs it wants to dynamically link
the libgcc.so. When you run it from the command line it will find your
system libgcc.so (which works) and so you don't see the segfault. When
you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get
your <cfebuilddir>/gcc directory which will find the libgcc.so that it
just built, which is the one
2007 Apr 01
3
[LLVMdev] trouble compiling llvm-gcc4 1.9
I'm having some trouble getting llvm-gcc4 to compile. It's unable to
compile darwin-crt3.c. It's mentioning "Complex expression. Absolute
segment assumed." but I'm not sure if that's a real error message. Has
anyone run into this before? I'm running on a G4 apple 10.4.8, kernel
version 8.6.0. I googled around and found a bug with the same error message:
2006 Nov 14
2
[LLVMdev] gcc 4 frontend binary for mac os x x86
Hi,
On Nov 13, 2006, at 9:17 PM, Tanya M. Lattner wrote:
> I assume you have an Mac with an Intel processor.
Yes. Sorry, I forgot to mentioned it in the mailbody.
> Download this:
> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz
I think that is the same tarball I used before.
> Let me know if that doesn't work.
Again: there is no fixheader-script like you
2006 Nov 14
0
[LLVMdev] gcc 4 frontend binary for mac os x x86
>> I assume you have an Mac with an Intel processor.
>
> Yes. Sorry, I forgot to mentioned it in the mailbody.
>
>> Download this:
>> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz
>
> I think that is the same tarball I used before.
Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is
a binary for llvm-gcc4 for Mac x86. You
2007 Jun 04
2
[LLVMdev] building llvm-gcc4 with a different target name
Hello,
I've put together a macports version of llvm and llvm-gcc4, but I've run
into a problem with how gcc on the mac works. llvm-gcc4 creates an
executable named:
/opt/local/bin/powerpc-apple-darwin8-gcc-4.0.1
Which happens to be the same executable in /usr/bin. Because I have
/opt/local before /usr/bin, gcc ends up using llvm-gcc4 to build all my
code. Most of the time this
2005 Oct 21
2
Yum update crashed, now I have lots of missing deps
During yum update my box crashed (I frequently have this on Centos 4
x86_64 boxes)
---> Package kdebase.x86_64 6:3.3.1-5.8 set to be updated
--> Running transaction check
--> Processing Dependency: system-config-printer = 0.6.116-1.centos4.1 for
package: system-config-printer-gui
--> Processing Dependency: glibc-devel = 2.3.4-2.9 for package: nptl-devel
--> Processing Dependency:
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
On Thu, 16 Nov 2006, Tanya M. Lattner wrote:
>> * I don't think this is ready for release. In particular the llvm-gcc4
>> binary
>> seg faults on FC 5 for most of llvm-test programs.
>> * I'm going to re-try without using the binaries and building
>> everything from scratch.
>
> Does llvm-gcc4 seg fault for make check? I've done extensive
2006 Dec 20
1
[LLVMdev] llvm build not respecting DESTDIR?
Reid Spencer wrote:
>> If not, does it make
>> sense to package the two in the two packages?
>> Macports is a source-based
>> packaging system, so it would seem odd to have to temporarily install
>> llvm-gcc to build llvm, but then install llvm-gcc in a separate package.
>>
>
> That issue goes away with llvm-gcc4. You would simply build llvm and