similar to: [LLVMdev] Changes to the llvm-gcc4 repository.

Still hasn't gone through yet. I'm predicting 11am EST. Cheers, -- Jim On Jul 31, 2006, at 7:18 PM, Jim Laskey wrote: > NOTE: Starting tomorrow (Aug 1, 2006) the llvm-gcc4 repository > will be moved to svn://anonsvn.opensource.apple.com/svn/llvm/ > trunk. This is to support tagging and future releases. > > I am told if you go to your llvm svn directory you can;

Apologies. Looks like the merges didn't take. I'll try and straighten this out today. Watch for the posting tomorrow. Cheers, -- Jim On Aug 1, 2006, at 7:59 AM, Jim Laskey wrote: > Still hasn't gone through yet. I'm predicting 11am EST. > > Cheers, > > -- Jim > > > > On Jul 31, 2006, at 7:18 PM, Jim Laskey wrote: > >> NOTE: Starting

Jim Laskey wrote: > NOTE: Starting tomorrow (Aug 1, 2006) the llvm-gcc4 repository will be > moved to svn://anonsvn.opensource.apple.com/svn/llvm/trunk. This is to > support tagging and future releases. Will this update live, or will it still synchronize nightly? Nick Lewycky

NOTE: Starting tomorrow (Aug 1, 2006) the llvm-gcc4 repository will be moved to svn://anonsvn.opensource.apple.com/svn/llvm/trunk. This is to support tagging and future releases. Cheers, -- Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060731/4172fba9/attachment.html> -------------- next

The svn llvm-gcc4 repository has now been successfully moved to svn:// anonsvn.opensource.apple.com/svn/llvm/trunk. (This is to support tagging and future releases.) You can do a fresh checkout; svn co svn://anonsvn.opensource.apple.com/svn/llvm/trunk $mydir or, I am told if you go to your llvm svn directory you can; svn switch --relocate svn://anonsvn.opensource.apple.com/svn/llvm \

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

There was a patch that went thru for this recently from Rafael Espindola. The fix is on the mirror. Index: gcc/dwarf2out.c =================================================================== --- gcc/dwarf2out.c (revision 120589) +++ gcc/dwarf2out.c (working copy) @@ -14361,9 +14361,8 @@ s->refcount++; /* Avoid unnecessarily putting strings that are used less than twice in the hash

I created the 1.9 release branch last night. As a reminder, please do not check in any code changes to the release branch. Please send me email if you have changes that need to be merged into the release branch. To check out the release branch: cvs -d <CVS Repository> co -r release_19 llvm cvs -d <CVS Repository> co -r release_19 llvm-test cvs -d <CVS Repository> co -r

Markus, We are in the process of trying to make this happen. It's a matter of getting all the duckings lined up in a row. We finally resigned ourselves to the fact that we can't cvs/svn and maintain the sanity of FSF branches, Apple branches and LLVM branches. So, over the next few working days we are going to set up a nightly cron script to checkout the latest and greatest

Dear guys, my llvm-gcc does not compile stdlib.h correctly. I found this explanation here: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=567 Indeed, I am running Mac OS 10.4. Do I have to rebuild my gcc front-end from source, or there is a script in the LLVM website that could help me? Best regards, Fernando

We are pleased to announce that it is now possible to download the sources of the llvm-gcc4 front end from a read-only mirror using subversion. To check out the code the first time use; svn co svn://anonsvn.opensource.apple.com/svn/llvm dst-directory After that, the code can be be updated in the destination directory using; svn update The mirror is brought up to date every evening.

Hi Tanya, I've been checking the state of the various llvm-test failures on X86/Linux with GCC 3.4.6 and llvm-gcc4. I haven't finished this, but I thought the following might be useful for other people that are testing the release on Linux. Each group of failing tests below is followed by a comment about why its failing. llc /MultiSource/Applications/oggenc/oggenc jit

Hi Koen, The process to build llvm-gcc as a crosscompiler is basically the same as build a normal gcc as crosscompiler. The differences: you need a LLVM installed (compiled for the host). You must configure llvm-gcc with --enable-llvm. Problems: - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the patch:

Rebuilding llvm-gcc4 from source should work fine. Please see the directions in the file README.LLVM at the top level src directory. You can check llvm-gcc4 out from Subversion with the command: svn co svn://anonsvn.opensource.apple.com/svn/llvm/trunk llvm-gcc4 Reid. On Sat, 2006-08-19 at 20:15 -0700, Fernando Magno Quintao Pereira wrote: > Dear guys, > > my llvm-gcc does not

It claims it was last updated 2007-01-04 06:47:31 -0400 (Thu, 04 Jan 2007). It should be close to TOT tomorrow. Cheers, -- Jim -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2417 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070104/9cecae71/attachment.bin>

>> Sorry for the delay, please try this tarball: >> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz > > There's some confusion with --enable-llvm configure parameter. I've built > LLVM to a separate build dir. The source is ~ghost/Work/llvm-cvs and build > dir is /space/p2/ghost/build/llvm-cvs ... > So, it seems like, at the same time: > > 1. buildir

The gcc4 tree is in svn. We believe it should be straight forward to create a public svn image but it will be late next week before we can set it up (minimal svn experience between Chris and myself.) Cheers, -- Jim On May 15, 2006, at 3:12 AM, Vladimir Prus wrote: > Chris Lattner wrote: > >> On Sat, 13 May 2006, Vladimir Prus wrote: >>>> If you're

Hi Tanya, Please apply these patches to the release branch: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039776.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039781.html Thanks, Evan On Nov 7, 2006, at 10:39 PM, Tanya M. Lattner wrote: > > I created the 1.9 release branch last night. As a reminder, please > do not > check

On 12/2/06, Jim Laskey <jlaskey at apple.com> wrote: > Rafael, > > Please bracket portions of your changes that involve modification of > C/C++ source code. For cases of modifying configuration scripts and > make files, use your best judgement. Obviously having the brackets > emitted in generated code is problematic (line numbers et cetera), so > don't bother in

Chris Lattner wrote: > On Thu, 2 Mar 2006, Vladimir Prus wrote: >>>> The instructions seem to have one path wrong. It says to get: >>> >>> I'll put together a tarball today. That will be easier than dealing >>> with a patch, and it will include a bunch of bugfixes since the previous >>> email. >> Further into process, I get this error: