similar to: [3.9 Release] Release Candidate 1 source and binaries available

Displaying 20 results from an estimated 30000 matches similar to: "[3.9 Release] Release Candidate 1 source and binaries available"

2016 Aug 22
2
[3.9 Release] Release Candidate 2 source and binaries available
We're getting close to the final release. I know the schedule on the web page says 'final' should be tagged today, but I still think it should be possible to get there this week. Source and binaries for LLVM-3.9.0-rc2 are now available at http://llvm.org/pre-releases/3.9.0/#rc2 Please try it out and let me know if you find any issues. As we're running out of time, RC2 will be a
2016 Aug 26
3
[3.9 Release] Release Candidate 3 source and binaries available
We're very very close to the final release. Source and binaries for LLVM-3.9.0-rc3 are available at http://llvm.org/pre-releases/3.9.0/#rc3 This release candidate is almost the same as rc2, with the following additional commits: r279224 - Minor change to OpenCL release notes r279260 - [lld] Add a note that 3.9 is a major milestone for us r279468, r279474 - Fix gather-root.ll SLP vectorizer
2016 Aug 20
4
[Release-testers] [3.9 Release] Release Candidate 2 has been tagged
Thanks! Can you post the sha1's for the files you uploaded? Windows and Mac look good. Uploaded: ca26fbfabb54ac1f70776ab3a5503313ec518f18 clang+llvm-3.9.0-rc2-x86_64-apple-darwin.tar.xz 26d616e1355dc0802f90babbd5ea0b72abc0c0bb LLVM-3.9.0-rc2-win32.exe 42363aeaff395d442f418d77b542a088b5b0658b LLVM-3.9.0-rc2-win64.exe Thanks, Hans On Fri, Aug 19, 2016 at 9:22 AM, Diana Picus <diana.picus
2016 Aug 19
8
[3.9 Release] Release Candidate 2 has been tagged
Dear testers, 3.9.0-rc2 was just tagged from the 3.9 branch at r279183. This is a release candidate in the very real sense that if nothing new comes up, this is be what the final release looks like. There are currently no open release blockers, and no patches in my merge-queue. Please build, test, and upload binaries to the sftp. Let me know how everything goes. >From this point, the branch
2016 Aug 20
2
[Release-testers] [3.9 Release] Release Candidate 2 has been tagged
It's a test for the new interceptor for prlimit. It could be disabled with __GLIBC_PREREQ for 2.13+. On Fri, Aug 19, 2016 at 5:16 PM, Hans Wennborg <hans at chromium.org> wrote: > +Evgenii for msan. > > I suspect the community simply doesn't keep track of what glibc > version is required :-/ > > On Fri, Aug 19, 2016 at 5:10 PM, Brian Cain <brian.cain at
2016 Aug 20
2
[Release-testers] [3.9 Release] Release Candidate 2 has been tagged
When I tested rc1 I found that some of the test suite wouldn't build on SLES11.3 as a consequence of changes to the tests. At least some of the msan tests have been changed leverage features of glibc newer than is available on this platform. I asked about a minimum-required glibc but didn't hear back. Is the minimum required glibc for 3.9 different from 3.8? When I tried rc1 on
2016 Jun 10
6
[3.9 Release] Release plan and call for testers
Hello everyone, It's time to start planning for the 3.9 release. Please let me know if you'd like to help providing binaries and testing for your favourite platform. I propose the following schedule: - 18 July: Create the release branch; build and test RC1 soon thereafter. - 1 August: Tag, build and test RC2. Any unfinished features need to be turned off by now. As we get closer to
2016 Jul 29
12
[3.9 Release] Release Candidate 1 has been tagged
Dear testers, 3.9.0-rc1 was just tagged from the 3.9 branch at r277207. This took a little longer than I'd hoped, but I think the branch is in a decent state now. There are still open merge requests and bugs, but I'd like to get the real testing started to see where we're at. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs,
2016 Aug 26
1
[cfe-dev] [3.9 Release] Release Candidate 3 source and binaries available
Hans, Are these new RC3 Windows binaries now with asserts disabled? Kind Regards Dan From: Hans Wennborg via cfe-dev<mailto:cfe-dev at lists.llvm.org> Sent: 26 August 2016 22:30 To: llvm-dev<mailto:llvm-dev at lists.llvm.org>; cfe-dev<mailto:cfe-dev at lists.llvm.org>; LLDB Dev<mailto:lldb-dev at lists.llvm.org>; openmp-dev (openmp-dev at
2017 Aug 14
4
[5.0.0 Release] Release Candidate 2 source and binaries available
Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc2 are now available at http://prereleases.llvm.org/5.0.0/#rc2 (I'll add more binaries as they become available.) Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including docs!), marking them blockers of http://llvm.org/pr33849. Cheers, Hans
2016 Feb 06
2
[3.8 Release] Release Candidate 2 source and binaries available
Hello everyone, Source, binaries and documentation for LLVM-3.8.0-rc2 is now available at http://llvm.org/pre-releases/3.8.0/#rc2 Please try them out, run tests, build your favourite projects, and *file bugs* about anything that doesn't work and needs to be fixed for the release. Please CC me on any findings. Many thanks to all our release testers and packagers for putting the binaries
2016 Jul 31
2
[Release-testers] [3.9 Release] Release Candidate 1 has been tagged
Hi, On the OpenMandriva side, x86_64 passes all checks. We're having some problems with other architectures though (see below): x86_64 succeeded, packages are here: https://abf.openmandriva.org/build_lists/76792 i586 fails to build, but this seems to be an issue with 3.8.1 (which we're using to build 3.9): /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
2020 Aug 03
2
[Release-testers] [11.0.0 Release] Release Candidate 1 is here
On Sat, Aug 1, 2020 at 3:22 PM Dimitry Andric <dimitry at andric.com> wrote: > > On 28 Jul 2020, at 19:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > > > We're a little bit behind schedule, but RC1 is now here. It was tagged > > earlier today as llvmorg-11.0.0-rc1. > > For this rc1, I used two patches, which are
2016 Aug 31
6
[3.9 Release] 'final' has been tagged
Dear testers, The final version of 3.9.0 was just tagged (from the 3.9 branch at r280312). There were no changes after rc3. This took a little longer than expected, but on the up side that means it's had more time to be tested. Please build the final binaries and upload to the sftp. For others following along: this means 3.9.0 is complete, but it will take a few days to get the tarballs
2020 Aug 17
2
[Release-testers] [11.0.0 Release] Release Candidate 1 is here
Thanks! Added to the release page now. PR44517 is marked as wontfix. Should we re-open it? PR44518 :-( Should we add this to the list or release blockers? On Tue, Aug 11, 2020 at 2:04 PM Diana Picus <diana.picus at linaro.org> wrote: > > Hi, > > Uploaded ARM & AArch64: > a60394b6508a9b66043f221f87eb4e2f5859f918f46e406b2c1e942d50ead7dc >
2018 Feb 07
12
[6.0.0 Release] Release Candidate 2 tagged
Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans
2017 Jan 18
19
[4.0.0 Release] Relase Candidate 1 has been tagged
Dear testers, 4.0.0-rc1 was just tagged from the branch, with r292377. There are still open merge requests and bugs, but I'd like to get the testing started to see what issues come up. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs, and your binaries to the web site once their ready. Thanks, Hans
2018 Jan 17
12
[6.0.0 Release] Release Candidate 1 tagged
Dear testers, Start your engines; 6.0.0-rc1 was just tagged. I know there are still open blockers and it's early in the process in a way, but I'd like to find out where we are. Please run the test script, let me know the results, and upload binaries. Thanks, Hans
2016 Dec 05
10
[4.0 Release] Schedule and call for testers
Dear everyone, There's still plenty of time left, but I'd like to get the schedule set before folks start disappearing for the holidays. Note that this release will also switch us to the new versioning scheme where the major version is incremented for each major release (i.e., when the 4.0 branch is created, trunk will become 5.0). If you'd like to help providing binaries and
2018 Feb 08
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. Built, tested and uploaded: SHA256