Hello testers, Start your engines, RC3 has just been tagged (at r229050 on the branch). If this one looks good, it will become the release. There has been quite a bit of activity on the branch since RC2; let's hope it's all goodness :-) Please let me know how it looks, and upload binaries to the sftp as usual. Thanks for all your efforts so far! - Hans
On Friday, February 13, 2015 11:46 AM, Hans Wennborg wrote:> Hello testers, > > Start your engines, RC3 has just been tagged (at r229050 on the > branch). If this one looks good, it will become the release. > > There has been quite a bit of activity on the branch since RC2; let's > hope it's all goodness :-) > > Please let me know how it looks, and upload binaries to the sftp as usual. > > Thanks for all your efforts so far!All looking good here, uploaded clang+llvm-3.6.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz Ben
Hi, Testing on OS X succeeded and looks good. Uploaded to SFTP, hash: MD5 (clang+llvm-3.6.0-rc3-x86_64-apple-darwin.tar.xz) e57b8eb53c10abb1829a7ce5c5113863 Cheers, Sebastian 2015-02-13 6:14 GMT+01:00 Ben Pope <benpope81 at gmail.com>:> On Friday, February 13, 2015 11:46 AM, Hans Wennborg wrote: >> >> Hello testers, >> >> Start your engines, RC3 has just been tagged (at r229050 on the >> branch). If this one looks good, it will become the release. >> >> There has been quite a bit of activity on the branch since RC2; let's >> hope it's all goodness :-) >> >> Please let me know how it looks, and upload binaries to the sftp as usual. >> >> Thanks for all your efforts so far! > > > All looking good here, uploaded > clang+llvm-3.6.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > Ben
Hello, On 13/02/2015 04:46, Hans Wennborg wrote:> Hello testers, > > Start your engines, RC3 has just been tagged (at r229050 on the > branch). If this one looks good, it will become the release. >I uploaded in Debian and it seems to build fine (thanks for landing the KFreebsd & hurd patches). However, there are some old regressions (so, they should not block 3.6) but they can be confusing. Some OrcJIT tests are failing (GNU/Linux Debian) http://llvm.org/bugs/show_bug.cgi?id=20586#c3 (I wrote a patch to silent them). There is also a critical issue on LLDB under GNU/Linux: http://lists.cs.uiuc.edu/pipermail/lldb-dev/2015-February/006575.html but it is not new either (but I think it is causing the lldb code coverage to be super low [1]). I don't know if it is specific to Debian or my options but it might affect others. Cheers, Sylvestre [1] http://llvm.org/reports/coverage/
Uploaded clang+llvm-3.6.0-rc3-mips-linux-gnu.tar.xz and
clang+llvm-3.6.0-rc3-mipsel-linux-gnu.tar.xz.
clang+llvm-3.6.0-rc3-mips-linux-gnu.tar.xz:
All good.
clang+llvm-3.6.0-rc3-mipsel-linux-gnu.tar.xz:
Still running test-suite.
clang+llvm-3.6.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz (cross compiling for
Mips):
All good.
microMIPS has two expected failures (smallpt and bullet) but microMIPS is
new to this release and is considered experimental because of these failures.
________________________________________
From: hwennborg at google.com [hwennborg at google.com] on behalf of Hans
Wennborg [hans at chromium.org]
Sent: 13 February 2015 03:46
To: Ben Pope; Renato Golin; Sylvestre Ledru; Dimitry Andric; Sebastian Dreßler;
Daniel Sanders; Nikola Smiljanić
Cc: llvmdev; cfe-dev
Subject: [3.6 Release] RC3 has been tagged
Hello testers,
Start your engines, RC3 has just been tagged (at r229050 on the
branch). If this one looks good, it will become the release.
There has been quite a bit of activity on the branch since RC2; let's
hope it's all goodness :-)
Please let me know how it looks, and upload binaries to the sftp as usual.
Thanks for all your efforts so far!
- Hans
What are the acceptable performance regressions in the generated
code for a llvm release? We seem to be badly regressed in some
benchmarks (which I first noticed from the review of 3.6-rc1 at
http://www.phoronix.com/scan.php?page=article&item=llvm-clang-3.5-3.6-rc1).
This same issue has also been reported in
http://llvm.org/bugs/show_bug.cgi?id=22058. In the case of the 22%
performance degradation in SciMark2's Sparse matmult benchmark, I have
identified both commits that contribute equally to this regression in
http://llvm.org/bugs/show_bug.cgi?id=22589...
Author: mcrosier
Date: Wed Sep 17 09:10:33 2014
New Revision: 217953
URL: http://llvm.org/viewvc/llvm-project?rev=217953&view=rev
Log:
[IndVarSimplify] Widen loop compare instructions.
This improves other optimizations such as LSR. A sext may be added to the
compare's other operand, but this can often be hoisted outside of the loop.
Added:
llvm/trunk/test/Transforms/IndVarSimplify/widen-loop-comp.ll
Modified:
llvm/trunk/lib/Transforms/Scalar/IndVarSimplify.cpp
llvm/trunk/test/Transforms/IndVarSimplify/no-iv-rewrite.ll
llvm/trunk/test/Transforms/IndVarSimplify/verify-scev.ll
and
Author: mzolotukhin
Date: Thu Nov 20 14:19:55 2014
New Revision: 222451
URL: http://llvm.org/viewvc/llvm-project?rev=222451&view=rev
Log:
Fix a trip-count overflow issue in LoopUnroll.
Currently LoopUnroll generates a prologue loop before the main loop
body to execute first N%UnrollFactor iterations. Also, this loop is
used if trip-count can overflow - it's determined by a runtime check.
However, we've been mistakenly optimizing this loop to a linear code for
UnrollFactor = 2, not taking into account that it also serves as a safe
version of the loop if its trip-count overflows.
Added:
llvm/trunk/test/Transforms/LoopUnroll/tripcount-overflow.ll
Modified:
llvm/trunk/lib/Transforms/Utils/LoopUnrollRuntime.cpp
llvm/trunk/test/Transforms/LoopUnroll/runtime-loop1.ll
Hopefully these issues can be triaged before the final release Better
a delayed release than one that is badly regressed in performance.
Jack
On Thu, Feb 12, 2015 at 10:46 PM, Hans Wennborg <hans at chromium.org>
wrote:> Hello testers,
>
> Start your engines, RC3 has just been tagged (at r229050 on the
> branch). If this one looks good, it will become the release.
>
> There has been quite a bit of activity on the branch since RC2; let's
> hope it's all goodness :-)
>
> Please let me know how it looks, and upload binaries to the sftp as usual.
>
> Thanks for all your efforts so far!
>
> - Hans
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
ARM binaries uploaded, seem to be working. I'll get the AArch64 on Monday, after I reset my board. Cheers, Renato On 13 Feb 2015 03:47, "Hans Wennborg" <hans at chromium.org> wrote:> Hello testers, > > Start your engines, RC3 has just been tagged (at r229050 on the > branch). If this one looks good, it will become the release. > > There has been quite a bit of activity on the branch since RC2; let's > hope it's all goodness :-) > > Please let me know how it looks, and upload binaries to the sftp as usual. > > Thanks for all your efforts so far! > > - Hans >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150216/d39b83e7/attachment.html>
Fedora and OpenSUSE binaries uploaded, all looking good. On Mon, Feb 16, 2015 at 3:17 AM, Renato Golin <renato.golin at linaro.org> wrote:> ARM binaries uploaded, seem to be working. I'll get the AArch64 on Monday, > after I reset my board. > > Cheers, > Renato > On 13 Feb 2015 03:47, "Hans Wennborg" <hans at chromium.org> wrote: > >> Hello testers, >> >> Start your engines, RC3 has just been tagged (at r229050 on the >> branch). If this one looks good, it will become the release. >> >> There has been quite a bit of activity on the branch since RC2; let's >> hope it's all goodness :-) >> >> Please let me know how it looks, and upload binaries to the sftp as usual. >> >> Thanks for all your efforts so far! >> >> - Hans >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150217/28f06413/attachment.html>
On 15 February 2015 at 16:17, Renato Golin <renato.golin at linaro.org> wrote:> ARM binaries uploaded, seem to be working. I'll get the AArch64 on Monday, > after I reset my board.AArhc64 binaries good. Uploaded. cheers, --renato
Hi Jack, On Sun, Feb 15, 2015 at 6:05 AM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote:> What are the acceptable performance regressions in the generated > code for a llvm release? We seem to be badly regressed in some > benchmarks (which I first noticed from the review of 3.6-rc1 at > http://www.phoronix.com/scan.php?page=article&item=llvm-clang-3.5-3.6-rc1). > This same issue has also been reported in > http://llvm.org/bugs/show_bug.cgi?id=22058. In the case of the 22% > performance degradation in SciMark2's Sparse matmult benchmark, I have > identified both commits that contribute equally to this regression in > http://llvm.org/bugs/show_bug.cgi?id=22589...Thank you very much for trying out the release candidate. I asked a few of the other developers, and the consensus was that while unfortunate, we won't block the release on a perf regression like this, at least not at this stage in the release process. Having said that, we will be doing an rc4, and Hal said that he or Sanjoy might be able to squeeze in a patch for the issue you pointed out before that. Otherwise, it will have to wait to 3.6.1 or 3.7. Thanks, Hans
On Thu, Feb 12, 2015 at 7:46 PM, Hans Wennborg <hans at chromium.org> wrote:> Hello testers, > > Start your engines, RC3 has just been tagged (at r229050 on the > branch). If this one looks good, it will become the release. > > There has been quite a bit of activity on the branch since RC2; let's > hope it's all goodness :-) > > Please let me know how it looks, and upload binaries to the sftp as usual.Windows binary uploaded: bd2001cf66c04a6fc2722cfeaf7b76c4b9c9c1ff LLVM-3.6.0-rc3-win32.exe It was built with the attached script. - Hans -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm_360._bat_ Type: application/octet-stream Size: 2380 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150217/9dce0c28/attachment.obj>
Possibly Parallel Threads
- [LLVMdev] [3.6 Release] RC3 has been tagged
- [LLVMdev] [cfe-dev] [3.6 Release] RC3 has been tagged
- [LLVMdev] [cfe-dev] [3.6 Release] RC3 has been tagged
- [LLVMdev] [cfe-dev] [3.6 Release] RC3 has been tagged
- [LLVMdev] [cfe-dev] [3.6 Release] RC3 has been tagged