Displaying 20 results from an estimated 30000 matches similar to: "[3.9 Release] Release Candidate 2 source and binaries available"
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 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
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 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
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
2016 Aug 04
2
[3.9 Release] Release Candidate 1 source and binaries available
Source and binaries for LLVM-3.9.0-rc1 are now available at
http://llvm.org/pre-releases/3.9.0/#rc1
Please try it 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.
Thanks,
Hans
2017 Aug 11
9
[5.0.0 Release] Release Candidate 2 tagged
Dear testers,
5.0.0-rc2 was just tagged.
I know we still have a bunch of open release blockers, but there has
been a lot of merged patches and I'd like to find out what the status
is.
Please build, test and upload binaries to the sftp. When uploading,
make sure to use the /data/testers-uploads/ directory on the server.
Let me know if there are any issues.
I'll upload sources, docs and
2020 Feb 13
14
[10.0.0 Release] Release Candidate 2 is here
Hello everyone,
Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It
includes 98 commits since the previous release candidate.
Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc2 and
https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2
Pre-built binaries will be added as they become available.
Please file bug reports for any issues
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
2018 Feb 13
0
[Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Hi Hans,
I'm seeing one unexpected failure:
libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp
Test logs show:
Standard Error:
--
terminating with uncaught exception of type std::length_error: basic_string
--
but only on my big endian MIPS machine. I have filed PR36373 for the above failure.
I've looked at the failures
2017 Aug 11
2
[Release-testers] [5.0.0 Release] Release Candidate 2 tagged
I'm not aware of a bug filed for this, so please file one. I don't
know much about the workings of test-suite myself, though.
On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain <brian.cain at gmail.com> wrote:
> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be
> failing for me with SIGILL. I'm guessing that my host CPU doesn't support
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 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 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 Mar 13
13
[10.0.0 Release] Release Candidate 4 is here
Hello everyone,
Release Candidate 4 was tagged earlier today as llvmorg-10.0.0-rc4 on
the release branch at b406eab8880. It contains 12 commits since the
previous release candidate.
If no new problems arise, this is what the final release will look like.
Source code and docs are available at
https://prereleases.llvm.org/10.0.0/#rc4 and
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
2017 Feb 09
7
[4.0.0 Release] Release Candidate 2 has been tagged
Hello testers,
4.0.0-rc2 was just tagged from the branch at r294535.
There are still open relase blocking bugs and merge requests, so this
will not be the last release candidate, but we've had a lot of merges
since the last one, and I'd like to see what the testing looks like.
The test-release.sh script was updated to also include lld. Make sure
you're using the latest version of
2017 Aug 25
9
[5.0.0 Release] Release Candidate 3 tagged
Dear testers,
5.0.0-rc3 was just tagged.
This is a release candidate in the real sense: if nothing bad comes up
in testing, this is what the release is going to look like.
Please build, test and upload binaries to the sftp (use the
/data/testers-uploads/ directory) and let me know what issues remain.
I know we're a little bit behind schedule, but hopefully we can get to
'final'