LLVMers, 2.6 pre-release1 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ You will notice that we have quite a few pre-compiled binaries (of both clang and llvm-gcc). We have identified several bugs that will be fixed in pre-release2, so please search the bug database before filing a new bug. If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check, report any failures (FAIL or unexpected pass). Note that you need to reconfigure llvm with llvm-gcc in your path or with -- with-llvmgccdir 3) Run "make TEST=nightly report" and send me the report.nightly.txt To test clang: 1) Compile llvm and clang from source. 2) Run make check for llvm. 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or unexpected passes) When reporting your results, please provide details on what platform you compiled on, and how you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! Thanks, Tanya Lattner -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090830/91917b55/attachment.html>
On Sun, Aug 30, 2009 at 10:50:34PM -0700, Tanya Lattner wrote:> LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of both > clang and llvm-gcc). We have identified several bugs that will be fixed > in pre-release2, so please search the bug database before filing a new > bug. > > If you have time, I'd appreciate anyone who can help test the release. > > To test llvm-gcc: > > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a pre- > compiled llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to reconfigure llvm with llvm-gcc in your path or with -- > with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txt > > > To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes) > > When reporting your results, please provide details on what platform you > compiled on, and how > you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. > > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! > > Thanks, > Tanya Lattner >> _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdevTanya, Chris said he would talk to you about adding... Author: lattner Date: Tue Aug 25 23:56:30 2009 New Revision: 80071 URL: http://llvm.org/viewvc/llvm-project?rev=80071&view=rev Log: "Current llvm-gcc-4.2 for trunk and the 2.6 release is unable to build the i386 multilib for the x86_64-apple-darwin target. The attached patch provides this support." Approved by Mike Stump, patch by Jack Howarth! Modified: llvm-gcc-4.2/trunk/gcc/config/i386/t-darwin64 Modified: llvm-gcc-4.2/trunk/gcc/config/i386/t-darwin64 URL: http://llvm.org/viewvc/llvm-project/llvm-gcc-4.2/trunk/gcc/config/i386/t-darwin64?rev=80071&r1=80070&r2=80071&view=diff to the llvm-gcc-4.2 2.6 branch. Can we get that done for the 2.6 release so that llvm-gcc-4.2 built as x86_64-apple-darwin can also generate i386 code via the i386 multilib as it should? Jack
Tanya Lattner wrote:> LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in pre-release2, so please search the bug database before filing > a new bug. > > If you have time, I'd appreciate anyone who can help test the release. > > To test llvm-gcc: > > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to reconfigure llvm with llvm-gcc in your path or with > --with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txt > > > To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes) > > When reporting your results, please provide details on what platform > you compiled on, and how > you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. > > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! > > Thanks, > Tanya Lattner > >Tanya, I can take up the clang part of testing. - Sanjiv> ------------------------------------------------------------------------ > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Here are the results for clang testing.
****************************************************
Macine details:
Linux 2.6.28-11-server #42-Ubuntu SMP i686 GNU/Linux.
****************************************************
****************************************************
Configured as srcdir != objdir with clang.
****************************************************
*****************************************************
Results of make check on top level objs directory.
*****************************************************
# of expected passes 4126
# of expected failures 26
make[1]: Leaving directory `/home/i00171/2.6/objs/test'
*****************************************************
Results of make -C tools/clang test VERBOSE=1
*****************************************************
Running 1461 tests, 2 threads.
Failing Tests (2):
/home/i00171/2.6/llvm-2.6/tools/clang/test/CodeGen/flexible-array-init.c
/home/i00171/2.6/llvm-2.6/tools/clang/test/CodeGenObjC/debug-info-linkagename.m
Failures: 2
make[1]: *** [all] Error 1
make[1]: Leaving directory `/home/i00171/2.6/objs/tools/clang/test'
make: *** [test] Error 2
make: Leaving directory `/home/i00171/2.6/objs/tools/clang'
Sanjiv Gupta wrote:> Tanya Lattner wrote:
>
>> LLVMers,
>>
>> 2.6 pre-release1 is ready to be tested by the community.
>> http://llvm.org/prereleases/2.6/
>>
>> You will notice that we have quite a few pre-compiled binaries (of
>> both clang and llvm-gcc). We have identified several bugs that will be
>> fixed in pre-release2, so please search the bug database before filing
>> a new bug.
>>
>> If you have time, I'd appreciate anyone who can help test the
release.
>>
>> To test llvm-gcc:
>>
>> 1) Compile llvm from source and untar the llvm-test in the projects
>> directory (name it llvm-test or test-suite). Choose to use a
>> pre-compiled llvm-gcc or re-compile it yourself.
>> 2) Run make check, report any failures (FAIL or unexpected pass). Note
>> that you need to reconfigure llvm with llvm-gcc in your path or with
>> --with-llvmgccdir
>> 3) Run "make TEST=nightly report" and send me the
report.nightly.txt
>>
>>
>> To test clang:
>> 1) Compile llvm and clang from source.
>> 2) Run make check for llvm.
>> 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or
>> unexpected passes)
>>
>> When reporting your results, please provide details on what platform
>> you compiled on, and how
>> you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc.
>>
>> Please COMPLETE ALL TESTING BY end of the day on Sept. 5th!
>>
>> Thanks,
>> Tanya Lattner
>>
>>
>>
> Tanya,
> I can take up the clang part of testing.
>
>
> - Sanjiv
>
>
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
On Aug 30, 2009, at 10:50 PM, Tanya Lattner wrote:> LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will > be fixed in pre-release2, so please search the bug database before > filing a new bug. > > If you have time, I'd appreciate anyone who can help test the release. > >I'm running the G5 PPC tests right now. Results will be slow for sure. :) -bw
Hi Tanya, The sources weren't updated for this pre-release testing. So I had the same problems on PPC. -bw On Sun, Aug 30, 2009 at 10:50 PM, Tanya Lattner<lattner at apple.com> wrote:> LLVMers, > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > You will notice that we have quite a few pre-compiled binaries (of both > clang and llvm-gcc). We have identified several bugs that will be fixed in > pre-release2, so please search the bug database before filing a new bug. > If you have time, I'd appreciate anyone who can help test the release. > To test llvm-gcc: > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a pre-compiled > llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). Note that > you need to reconfigure llvm with llvm-gcc in your path or with > --with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txt > > To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes) > When reporting your results, please provide details on what platform you > compiled on, and how > you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! > Thanks, Tanya Lattner > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >
Hi Tanya, I have tried the 2.6 pre-release on the following host : Windows XP pro SP2 with mingw/msys : uname -a MINGW32_NT-5.1 OLIVE 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown gcc -v Reading specs from d:/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry --disable-shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchronization --enable-libstdcxx-debug Thread model: win32 gcc version 3.4.5 (mingw special) - srcDir != objDir - The build went fine. (configure and make) - llvm make check : not possible under mingw (dejagnu...) - clang make check fails : Every call to clang binary ends like this : ./Release/bin/clang foo.c Stack dump: 0. Program arguments: d:/llvm/llvm-2.6/build/Release/bin/clang-cc.exe -triple i386-pc-mingw32 -S -disable-free -main-file-name foo.c --relocation-model static --disable-fp-elim --unwind-tables=0 --mcpu=pentium4 --fmath-errno=1 -fdiagnostics-show-option -o C:/Temp/cc-000000.s -x c foo.c 77C42A16 (0x0022F958 0x0167C757 0x0022F988 0x0167CBE8), wscanf()+1872 bytes(s) 77C3F962 (0x0022F9B0 0x0167C757 0x0167CBE8 0xFFFFFFFF), sprintf()+0049 bytes(s) 0046DA0C (0x10202000 0x20101010 0x20202020 0x60404020) 01AED7D4 (0x015B9F80 0x015B8590 0x015B9070 0x0081BC20) <unknown module> 01107940 (0x95340800 0x24048901 0x71ECFBE8 0x0CC483FF) C7102444 (0x00000000 0x00000000 0x00000000 0x00000000) <unknown module> clang: error: compiler command failed due to signal 1073741819 (use -v to see invocation) A debug build fails on the same problem : ./Debug/bin/clang foo.c Stack dump: 0. Program arguments: d:/llvm/llvm-2.6/build_debug/Debug/bin/clang-cc.exe -triple i386-pc-mingw32 -S -disable-free -main-file-name foo.c --relocation-model static --disable-fp-elim --unwind-tables=0 --mcpu=pentium4 --fmath-errno=1 -fdiagnostics-show-option -o C:/Temp/cc-000000.s -x c foo.c 77C42A16 (0x0022F948 0x01354530 0x0022F978 0x121CC7A8), wscanf()+1872 bytes(s) 77C3F962 (0x0022F9A0 0x01354530 0x013548FD 0xFFFFFFFF), sprintf()+0049 bytes(s) 0043EC6D (0x013548FD 0x00000040 0x01354896 0x00000001) 0043F2C5 (0x003D4068 0x121CC1F4 0x0022FAD0 0x01354BC9) 0043F90C (0x121CC1F0 0x0022FB20 0x0022FD00 0x003D4068) 010C2752 (0x0022FC50 0x0022FE10 0x0022FD00 0x003D4068) 00406086 (0x00000013 0x003D3F90 0x003D3028 0x015CF000) 0040124B (0x00000001 0x00000009 0x0022FFF0 0x7C816FE7) 00401298 (0x002420A8 0x0022F1E8 0x7FFD7000 0xC0000005) 7C816FE7 (0x00401280 0x00000000 0x78746341 0x00000020), RegisterWaitForInputIdle()+0073 bytes(s) clang: error: compiler command failed due to signal 1073741819 (use -v to see invocation) Here is the stack trace, I try to re-build : ___mingw_CRTStartup _main (anonymous namespace)::DriverPreprocessorFactory::CreatePreprocessor() clang::InitializePreprocessor(clang::Preprocessor&, clang::PreprocessorInitOptions const&) clang::InitializePredefinedMacros(clang::TargetInfo const&, clang::LangOptions const&, std::vector<char, std::allocator<char> >&) clang::DefineTypeSize(char const*, unsigned int, char const*, bool, std::vector<char, std::allocator<char> >&) _sprintf The "faulty" call to DefineTypeSize is the 5th. The one which used a "long long" type. In the method DefineTypeSize, the call to sprintf is as follow : sprintf(MacroBuf, "%s=%llu%s", MacroName, MaxVal, ValSuffix); and should be transformed to : sprintf(MacroBuf, "%s=%I64u%s", MacroName, MaxVal, ValSuffix); as mingw toolchain don't support "%llu" marker. With this correction, clang seems to work on this platform. I wanted to provide a patch but I'm not able to find something like "LLVM_ON_MINGW" macro definition. Sorry. :( . Thanks for your work ! Cheers, Olivier. On Wed, Sep 2, 2009 at 10:19 PM, Bill Wendling <isanbard at gmail.com> wrote:> Hi Tanya, > > The sources weren't updated for this pre-release testing. So I had the > same problems on PPC. > > -bw > > On Sun, Aug 30, 2009 at 10:50 PM, Tanya Lattner<lattner at apple.com> wrote: > > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of both > > clang and llvm-gcc). We have identified several bugs that will be fixed > in > > pre-release2, so please search the bug database before filing a new bug. > > If you have time, I'd appreciate anyone who can help test the release. > > To test llvm-gcc: > > 1) Compile llvm from source and untar the llvm-test in the projects > > directory (name it llvm-test or test-suite). Choose to use a pre-compiled > > llvm-gcc or re-compile it yourself. > > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that > > you need to reconfigure llvm with llvm-gcc in your path or with > > --with-llvmgccdir > > 3) Run "make TEST=nightly report" and send me the report.nightly.txt > > > > To test clang: > > 1) Compile llvm and clang from source. > > 2) Run make check for llvm. > > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > > unexpected passes) > > When reporting your results, please provide details on what platform you > > compiled on, and how > > you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. > > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! > > Thanks, Tanya Lattner > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090903/b0b90af6/attachment.html>
Hi Tanya, building llvm-2.6 on x86-64 linux with gcc-4.4 I see the following warnings (also present on mainline): llvm-2.6/runtime/libprofile/CommonProfiling.c: In function ‘write_profiling_data’: llvm-2.6/runtime/libprofile/CommonProfiling.c:103: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:104: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:105: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:108: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:114: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:115: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result llvm-2.6/runtime/libprofile/CommonProfiling.c:116: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result Results (llvm-gcc built from source): "make check" -> 1 unexpected success (FrontendC/2009-08-11-AsmBlocksComplexJumpTarget.c) I think Dale fixed this on mainline.> To test llvm-gcc: > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to reconfigure llvm with llvm-gcc in your path or with > --with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txtI've attached report.nightly.txt.> To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes)No failures or unexpected passes. Many warnings about aliasing problems during the build (see PR4061).> When reporting your results, please provide details on what platform you > compiled on,x86-64 ubuntu (karmic) linux and how> you built LLVM (src == obj, or src != obj),clang, and/or llvm-gcc.src != obj for all, llvm-gcc configured with: --enable-languages=c,c++,fortran> > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th!Thanks for taking care of the release! Best wishes, Duncan. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: report.nightly.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090904/e181b403/attachment.txt>
Just a reminder that this should be wrapping up by end of day tomorrow. There are several 2.6 bugs, so we might be pushing the release out a week to get those all fixed. I'll update once I know more. -Tanya On Aug 30, 2009, at 10:50 PM, Tanya Lattner wrote:> LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will > be fixed in pre-release2, so please search the bug database before > filing a new bug. > > If you have time, I'd appreciate anyone who can help test the release. > To test llvm-gcc: > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a pre- > compiled llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). > Note that you need to reconfigure llvm with llvm-gcc in your path or > with --with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txt > > To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures > or unexpected passes) > > When reporting your results, please provide details on what platform > you compiled on, and how > you built LLVM (src == obj, or src != obj), clang, and/or llvm-gcc. > > Please COMPLETE ALL TESTING BY end of the day on Sept. 5th! > Thanks, Tanya Lattner >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090904/a0cbc3ae/attachment.html>
On 2009-08-31 08:50, Tanya Lattner wrote:> LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ >Hi Tanya, Here are the results for x86_64 Linux (Debian unstable):> You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in pre-release2, so please search the bug database before filing > a new bug. > > If you have time, I'd appreciate anyone who can help test the release. > To test llvm-gcc: > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to reconfigure llvm with llvm-gcc in your path or with > --with-llvmgccdir > 3) Run "make TEST=nightly report" and send me the report.nightly.txtBuilt from source, objdir != srcdir ../llvm-gcc4.2-2.6.source/configure --program-prefix=llvm- --enable-llvm=/home/edwin/llvm2.6/obj/ --enable-languages=c,c++,fortran XPASS: /home/edwin/llvm2.6/llvm-2.6/test/FrontendC/2009-08-11-AsmBlocksComplexJumpTarget.c> > To test clang: > 1) Compile llvm and clang from source. > 2) Run make check for llvm. > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes)Tests OK. Some further testing I did (not all PRs here are regressions): ClamAV (latest git): clang OK, llvm-gcc OK Linux 2.6.31-rc8 (patched) build fails for both: ARCH=x86: clang: PR4689, llvm-gcc/clang: PR4628 ARCH=um: clang: PR4096, PR4689, llvm-gcc: PR4898 (note that at some point LLVM was able to compile these, not sure if it was 2.5, or after 2.5) Perl 5.10: clang: build OK, 1 test fails PR4897 llvm-gcc: OK valgrind 3.4.1: clang: build fails PR2461, PR4899; llvm-gcc build OK, test build fails PR4434 ACE_wrappers: llvm-gcc OK blender 2.49b: llvm-gcc build OK, render matches gcc where render is deterministic, and mean-square-error is about the same where not clang build OK (building only C sources), renders some blend files differently, particularly around shaded regions: PR4900 Best regards, --Edwin
On 2009-09-05 11:56, Török Edwin wrote:> On 2009-08-31 08:50, Tanya Lattner wrote: > >> LLVMers, >> >> 2.6 pre-release1 is ready to be tested by the community. >> http://llvm.org/prereleases/2.6/ >> >> > > Hi Tanya, > > Here are the results for x86_64 Linux (Debian unstable): > > >> You will notice that we have quite a few pre-compiled binaries (of >> both clang and llvm-gcc). We have identified several bugs that will be >> fixed in pre-release2, so please search the bug database before filing >> a new bug. >> >> If you have time, I'd appreciate anyone who can help test the release. >> To test llvm-gcc: >> 1) Compile llvm from source and untar the llvm-test in the projects >> directory (name it llvm-test or test-suite). Choose to use a >> pre-compiled llvm-gcc or re-compile it yourself. >> 2) Run make check, report any failures (FAIL or unexpected pass). Note >> that you need to reconfigure llvm with llvm-gcc in your path or with >> --with-llvmgccdir >> 3) Run "make TEST=nightly report" and send me the report.nightly.txt >> > >Attached report.nightly.txt.> Built from source, objdir != srcdir > ../llvm-gcc4.2-2.6.source/configure --program-prefix=llvm- > --enable-llvm=/home/edwin/llvm2.6/obj/ --enable-languages=c,c++,fortran > > XPASS: > /home/edwin/llvm2.6/llvm-2.6/test/FrontendC/2009-08-11-AsmBlocksComplexJumpTarget.c > > > >> To test clang: >> 1) Compile llvm and clang from source. >> 2) Run make check for llvm. >> 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or >> unexpected passes) >> > > Tests OK. > > Some further testing I did (not all PRs here are regressions): > > ClamAV (latest git): clang OK, llvm-gcc OK > > Linux 2.6.31-rc8 (patched) build fails for both: > ARCH=x86: clang: PR4689, llvm-gcc/clang: PR4628 > ARCH=um: clang: PR4096, PR4689, llvm-gcc: PR4898 > (note that at some point LLVM was able to compile these, not sure if it > was 2.5, or after 2.5) > > Perl 5.10: > clang: build OK, 1 test fails PR4897 > llvm-gcc: OK > valgrind 3.4.1: > clang: build fails PR2461, PR4899; > llvm-gcc build OK, test build fails PR4434 > ACE_wrappers: llvm-gcc OK > blender 2.49b: > llvm-gcc build OK, render matches gcc where render is > deterministic, and mean-square-error is about the same where not > clang build OK (building only C sources), renders some blend > files differently, particularly around shaded regions: PR4900 > > Best regards, > --Edwin >-------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: report.nightly.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090905/2360eb3a/attachment.txt>