search for: r99160

...; 2) Run make check for llvm. > > 3) Run make -C tools/clang-2.6 test VERBOSE=1 (report any failures or > unexpected passes) Surely you meant tools/clang-2.7 FYI I pulled the following revisions for ClamAV's llvm on top of 2.7: r98349 r98410 r98447 r98508 r99143 r99146 r99147 r99160 r99400 I don't know if any of these qualify as regression fixes for 2.7, I'll leave it up to you to decide if you want to put them into 2.7 or not. Best regards, --Edwin -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: report.nightly.t...

...-2.6 test VERBOSE=1 (report any failures or >> unexpected passes) > > Surely you meant tools/clang-2.7 > Yes. > FYI I pulled the following revisions for ClamAV's llvm on top of 2.7: > r98349 > r98410 > r98447 > r98508 > r99143 > r99146 > r99147 > r99160 > r99400 > > I don't know if any of these qualify as regression fixes for 2.7, I'll > leave it up to you to decide if you want to put them into 2.7 or not. > I'll have to discuss with Chris about these. Its technically not a release blocker. Thanks, -Tanya > Best...

The 2.7 binaries are available for testing: http://llvm.org/pre-releases/2.7/pre-release1/ You will also find the source tarballs there as well. We rely on the community to help make our releases great, so please help test 2.7 if you can. Please follow these instructions to test 2.7: To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it

...t; unexpected passes) >> Surely you meant tools/clang-2.7 >> > > Yes. > >> FYI I pulled the following revisions for ClamAV's llvm on top of 2.7: >> r98349 >> r98410 >> r98447 >> r98508 >> r99143 >> r99146 >> r99147 >> r99160 >> r99400 >> >> I don't know if any of these qualify as regression fixes for 2.7, I'll >> leave it up to you to decide if you want to put them into 2.7 or not. >> > > I'll have to discuss with Chris about these. Its technically not a release blocker....