Displaying 20 results from an estimated 11000 matches similar to: "[LLVMdev] llvm-gcc4_2"
2007 Mar 28
2
[LLVMdev] llvm-gcc4_2
hi
> > i fixed some major bugs in the llvm-gcc4_2 patch since my last post.
> > this brings me to an interesting question:
> >
> > what are your criteria to use my patch for further development?
>
> I have no fixed criteria. I think the best solution is for the work to be
> checked into the (forthcoming) public SVN server. When it is available,
> you can
2007 Jul 02
1
[LLVMdev] svn repository, llvm-gcc4.2
hi!
i was working on an llvm-gcc4_2 version, which i used as a starting-point for
a fixed-point c-datatype implementation.
i read that the svn repos is up now, and so i remembered the following lines:
> On Fri, 23 Mar 2007, Peter Wiedermann wrote:
> > i fixed some major bugs in the llvm-gcc4_2 patch since my last post.
> > this brings me to an interesting question:
> >
2007 Jul 03
1
[LLVMdev] svn repository, llvm-gcc4.2
> > i was working on an llvm-gcc4_2 version, which i used as a starting-point for
> > a fixed-point c-datatype implementation.
> > i read that the svn repos is up now, and so i remembered the following lines:
> >
> >> On Fri, 23 Mar 2007, Peter Wiedermann wrote:
> >>> i fixed some major bugs in the llvm-gcc4_2 patch since my last post.
>
2007 Mar 20
0
[LLVMdev] llvm-gcc4_2, llvm-gcc4_2-fixed-point
hi!
because i read that other people may be interested
in llvm-gcc4_2 in the google-soc thread, here is the
status of my work:
i merged llvm-gcc and the current gcc4_2.
this is the patch from official gcc4_2 to my llvm-gcc4_2:
http://geldspeicher.entenhausen.at/dl/gcc-4_2_to_llvm.patch.gz
comments:
+ i left out most APPLE LOCAL* marked regions of llvm-gcc4 which
were not concerning llvm
2007 Mar 30
0
[LLVMdev] llvm-gcc4_2
On Wed, 28 Mar 2007, Peter Wiedermann wrote:
> ok, thats fine to me.
> i think the worst part of the work is done.
wow, you look quite far along.
>> Hrm, that's strange. llvm-test doesn't pass 100% (e.g. some of the EH
>> stuff is now working yet), but it should ahve basic functionality. What
>> is broken?
>>
>
> major error causes:
>
> the
2007 Mar 30
0
[LLVMdev] llvm-gcc4_2
On Thu, 29 Mar 2007, Reid Spencer wrote:
> On Thu, 2007-03-29 at 23:47 -0800, Chris Lattner wrote:
>
>> Very nice. Reid/Anton, do you guys have an idea when the svn server will
>> be available?
>
> Mid April.
>
> The SVN server is getting installed tomorrow. Anton and I are still
> testing the automated conversion script (almost there).
>
> We will probably
2007 Mar 30
2
[LLVMdev] llvm-gcc4_2
On Thu, 2007-03-29 at 23:47 -0800, Chris Lattner wrote:
> Very nice. Reid/Anton, do you guys have an idea when the svn server will
> be available?
Mid April.
The SVN server is getting installed tomorrow. Anton and I are still
testing the automated conversion script (almost there).
We will probably make a beta svn server available (via my machine) for
anyone that wants a preview.
One
2006 Aug 07
0
[LLVMdev] gcc4 or gcc3?
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
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]:
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 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
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
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
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 May 09
0
[LLVMdev] New llvmgcc4 snapshot
Hi,
i tried compiling llvmgcc4 on x86_64-linux. The two changes i needed to
apply to llvm and llvmgcc4 are attached. Those two patches tell llvmgcc4
to use the x86 code-generator for x86_64 and give x86_64-* targets a
score of 10 for the x86 backend when trying to find appropriate backends.
Now i'm getting stuck during the compile when an assertion is triggered:
make[3]: Leaving