similar to: [LLVMdev] LLVM 1.5 Release Branch Created

Alexander Friedman wrote: > On May 17, John Criswell wrote: > >>Dear All, >> >>I've finished building binaries for the GCC frontends and am now testing >> the 1.5 release branch on i386/Linux, Sparc/Solaris, and PowerPC/MacOS X. >> >>I'm looking for volunteers to test LLVM 1.5 on platforms that we don't >>have in house. I'm

Dear All, I've finished building binaries for the GCC frontends and am now testing the 1.5 release branch on i386/Linux, Sparc/Solaris, and PowerPC/MacOS X. I'm looking for volunteers to test LLVM 1.5 on platforms that we don't have in house. I'm specifically looking for people who can do: Itanium FreeBSD/i386 Windows (Cygwin, MingW, etc) I'm mainly interested in major

Sean Peisert wrote: > John, > > I may be missing something here, but if I the compilation docs, I need > to build LLVM first and the C frontend second. But doing this, I > get: > > **llvm-gcc/llvm-g++ was not found, > > (obviously -- it wasn't installed, right?) You do need to build LLVM first before building llvm-gcc. This may seem a bit weird, but

Dear All, Do people think that they are ready to create the LLVM 1.6 release branch? I believe all the development is pretty much done. Is all the documentation in the LLVM source tree updated and ready? I'm not able to make a full doc review like I've been able to do in previous releases, so I need volunteers to work on the docs if they're not done yet. -- John T. -- John

Misha Brukman wrote: > On Tue, May 17, 2005 at 01:20:48PM -0500, John Criswell wrote: > >>Personally, I never use "gmake check." >> >>What I do is checkout everything out, build it, run the tests in >>"llvm/test," and then run all of the tests in the llvm-test CVS >>module. > > > I think the nightly test script can be used for

Dear LLVM Developers, The LLVM website, CVS repository, and SAFECode website should now be back online. Should you encounter any problems with the LLVM services, please send email to llvmdev at cs.uiuc.edu so that we may fix it. Regards, John T. Criswell ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu

Dear All, Thanks to the testing done by Bill Wendling, we have the following list of regressions for PPC: TEST (cbe) 'exception_spec_test' FAILED! ******************** TEST (cbe) 'function_try_block' FAILED! ******************** Oopack (jit, llc, and cbe) also fails, but I don't know if that's a regression or not. I'm alright with releasing with these regressions

Hi, It looks like the CVS server is still not available. When I try to update with cvs, I get: cvs [update aborted]: connect to llvm-cvs.cs.uiuc.edu(128.174.245.58):2401 failed: Connection refused I know the server was down earlier this week but according to the message below, its supposted to be restored by now. Could someone please help? Thanks, Reid. On Wed, 2004-01-07 at 14:30, John T.

Chris Lattner wrote: > On Mon, 7 Nov 2005, John Criswell wrote: > >> Tanya Lattner wrote: >> >>> Everything builds fine on sparc. The configure script needs to be >>> fixed though (see previous email). >> >> >> I'm not getting the error with the configure script (on Kain, anyway). >> I've tried it with --with-f2c and with f96

Dear All, I have found the following regressions on Linux/i386: 176.gcc (cbe, llc, jit) 252.eon (cbe, llc, jit) 126.gcc (cbe, llc, jit) Named (llc, jit) I ran a quick test on 176.gcc, and it doesn't seem to be an optimization problem. -- John T. -- John T. Criswell Research Programmer University of Illinois at Urbana-Champaign "It's today!" said Piglet. "My favorite

Dear All, Our main server is back up, and all LLVM services (CVS, website, etc) should be up and available for use. If you notice that something is wrong, please send an email to llvmdev at cs.uiuc.edu. Thanks! -- John T. -- ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu * * Research Programmer

Dear All, I've created the LLVM release branch (CVS tag release_16). Those developers wanting to commit changes to LLVM without having your changes go into LLVM 1.6 can now commit to CVS mainline to your heart's content. :) TESTING: -------- 1. I'm still looking for volunteers to test MacOS X and Solaris. If you'd like to volunteer, please email the list to let us know.

Dear All, I would like to create the release branch for the llvm-gcc source code tomorrow morning. I imagine this will be okay as llvm-gcc seems pretty healthy and no one is currently doing any development on it. If there's something that needs to be fixed, or you're working on llvm-gcc, please email the list so that I can delay creating the branch as appropriate. I won't be

>> Everything builds fine on sparc. The configure script needs to be fixed >> though (see previous email). > > I'm not getting the error with the configure script (on Kain, anyway). I've > tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my > $PATH. I get the error with and without the --with-f2c option. I never used the NAG Fotran

Chris Morgan wrote: > Any reason not to upgrade to subversion? It does a much better job > with handling moved or renamed files although svn doesn't actually > store a 'move' or a 'rename' as a single versioned operation. We discussed moving to another revision control system about a year ago, if I recall correctly. At that time, we decided not to move to another

Cyrille Mescam wrote: > Morning, > > I would like to know if you received my mail with the assembly code > you wanted. > > It not, i'll send it again to you. > > Thanks for your help. > > Regards. > > Cyrille > I've looked into the files you sent me, and it seems that the problem is occuring due to the C library simplication pass (which is run

Dear All, Here is a more complete list of regressions for the platforms listed below. Some of the regressions from the previous list I emailed a few days ago have been fixed or were false positives. Thanks to all who've helped fix things. We would like to try to get as many of these fixed as possible before I create the release branch (still scheduled for tomorrow, Friday). I'll

Ricardo wrote: > Hello, > > Is PA working on the macintosh already? Although we may not have run it on MacOS X recently, I believe that it should work. We've run it on several architectures and operating systems, including SparcV9/Solaris. If you find that PA doesn't compile or work on MacOS X, please file a bug report (http://llvm.cs.uiuc.edu/bugs/) so that we can fix it.

Finn S Andersen wrote: > Chris Lattner wrote: > >> I can't reproduce this failure with mainline CVS using either lli or llc: >> >> $ lli -regalloc=linearscan a.out.bc >> $ echo $status >> 0 >> >> Are you sure that the CVS version is in your path? >> >> > After configure and make I run make install, which moves the executables

Dear LLVMers, Here is the current, tentative schedule for LLVM 1.5: 1. We are hoping to have all relevant features and bug fixes into mainline CVS by Friday of this week. For those of you with commit access, please plan to have all of your changes for LLVM 1.5 committed by 9 am (CST) this Friday. If you need more time, please email the list. 2. On Friday, I will be making the 1.5 release