similar to: [LLVMdev] llvm-gcc4.0 support dropped - please update testers

On Thu, Jun 5, 2008 at 2:50 PM, Tanya M. Lattner <tonic at nondot.org> wrote: > > >> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind > >> that you need to keep llvm-gcc in sync with llvm (same revision number). > > > > This basically means llvm-gcc needs to be rebuild every time llvm > > is built and the test run.

>>>> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind >>>> that you need to keep llvm-gcc in sync with llvm (same revision number). >>> >>> This basically means llvm-gcc needs to be rebuild every time llvm >>> is built and the test run. Shouldn't this be part of >>> NewNightlyTest.pl then? >> >>

>> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind >> that you need to keep llvm-gcc in sync with llvm (same revision number). > > This basically means llvm-gcc needs to be rebuild every time llvm > is built and the test run. Shouldn't this be part of > NewNightlyTest.pl then? Yes. Patches accepted ;) There is a GSOC student that is supposed

> I've run the test last night to see how long it takes, and I can > afford to cronjob it for the night. Great! > I didn't quite realize it would automatically send the report, but > it did [1] and there are a few test failure from the > Frontend{C,C++} directories. I suppose this is because I have > llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is >

Tanya M. Lattner wrote: >> Is >> there a specific version of llvm-gcc that is prefered for nightly >> tests? Shall I go with the latest stable one? 4.0 or 4.2? > llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind > that you need to keep llvm-gcc in sync with llvm (same revision number). This basically means llvm-gcc needs to be rebuild every time

Hello list! Tanya Lattner wrote: > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I've run the test last night to see how long it takes, and I can afford to cronjob it for the night. I didn't quite realize it would automatically

All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in

Dear Tanya: > You also have a few CBE failures that I am not seeing. What version > of xcode do you have installed? Xcode 2.4.1 > Can you send me the following files? > SingleSource/Regression/C/Output/2008-01-07-LongDouble.* > SingleSource/Regression/C/Output/PR1386.* OK, I attached those files (llvm-2.2-test-output.tar.gz) Best regards, 2008/1/30, Tanya Lattner <tonic at

My test results for the LLVM 2.2 prerelease. === Q. Target === * Mac OS X 10.4.11 * 2 GHz Intel Core 2 Duo * MacBook % uname -a Darwin macbook.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 === Q. How you built the release === * objDir != srcDir * Release build * llvm-gcc-4.2 from source

Thanks for testing the release. Overall the test results look decent with a couple exceptions. You also have a few CBE failures that I am not seeing. What version of xcode do you have installed? Can you send me the following files? SingleSource/Regression/C/Output/2008-01-07-LongDouble.* SingleSource/Regression/C/Output/PR1386.* Thanks, Tanya On Jan 26, 2008, at 6:43 AM, Takanori Ishikawa

More bison woes. llvm-2.1 + the patch Chris mentioned builds without bison, but llvm-gcc4 doesn't: /home/emil/ll/llvm-gcc4.0-2.1.source/missing bison -d -o gengtype-yacc.c ../../llvm-gcc4.0-2.1.source/gcc/gengtype-yacc.y WARNING: `bison' missing on your system. You should only need it if you modified a `.y' file. You may need the `Bison' package in order for

>> In addition to this, I've checked in the first draft of the release >> notes into llvm/docs/ReleaseNotes.html (http://llvm.org/docs/ >> ReleaseNotes.html). > > The release notes mention llvm-gcc 4.2, but the prerelease only included > llvm-gcc 4.0. Is the final release going to include 4.0 or 4.2 or both? I will be releasing a source tar ball of llvm-gcc4.2, but

On Sep 18, 2007, at 9:28 PM, Erick Tryzelaar wrote: > Tanya Lattner wrote: >> LLVMers, >> >> The 2.1 pre-release (version 1) is available for testing: >> http://llvm.org/prereleases/2.1/version1/ > > A couple months ago, I had a problem packaging llvm-gcc for macports > because one of the binaries from llvm-gcc was somehow getting used by > Apple's gcc

LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. Configuring in i686-pc-cygwin/libstdc++-v3 configure: creating cache ./config.cache checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes

On Sep 18, 2007, at 10:14 PM, Emil Mikulic wrote: > On Tue, Sep 18, 2007 at 10:14:29PM -0700, Tanya Lattner wrote: >> You can set the program-prefix to be "llvm-". We actually recommend >> this and its in the README.llvm. We do not require it though. > > I meant to bring this up: > > llvm-gcc4.0-2.1.source/README.LLVM makes no mention of > passing

On Tue, Sep 18, 2007 at 10:32:54PM -0700, Tanya Lattner wrote: > On Sep 18, 2007, at 10:14 PM, Emil Mikulic wrote: > > llvm-gcc4.0-2.1.source/README.LLVM makes no mention of > > passing --program-prefix=llvm- to configure. > > Well, it does in trunk. I just forgot to merge it over. Thanks for > the reminder ;) >

Rajika, A couple of comments: - You should provide a way to specify where llvm-gcc is built (just like llvm). - I would highly recommend allowing the user to only update llvm-gcc and not check it out from scratch each time. Checking out llvm-gcc is very time consuming. You would need to make sure that llvm and llvm-gcc have the same rev number and nuke the llvm obj/install dirs so you get a

On Saturday 15 September 2007, Tanya Lattner wrote: > 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source. > Compile everything. Run "make check" and the full llvm-test suite > (make TEST=nightly report). I tried to do this, but ran into trouble. LLVM itself compiled fine. GCC compilation is broken when Java support is enabled. I can file a detailed bug report

On Tue, Sep 18, 2007 at 10:14:29PM -0700, Tanya Lattner wrote: > You can set the program-prefix to be "llvm-". We actually recommend > this and its in the README.llvm. We do not require it though. I meant to bring this up: llvm-gcc4.0-2.1.source/README.LLVM makes no mention of passing --program-prefix=llvm- to configure. ISTR Reid suggesting this option to me a long time ago.

Hello, On Jun 3, 2008, at 08:52 , Tanya Lattner wrote: > All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I think I might be able to set up a nightly tester for Linux x86 (32- bit). Although I've been following LLVM for