similar to: [6.0.0 Release] Release Candidate 3 source, docs and binaries available

Hello everyone, Source, docs and binaries for LLVM-6.0.0-rc2 are now available at http://prereleases.llvm.org/6.0.0/#rc2 I'll add more binaries as they become available. Please report any problems you find, ideally as bugs marked as blockers of http://llvm.org/PR35804 Thanks, Hans

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

Hi, No major issues seen so far for mips. Binaries uploaded. SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)= 54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d61 SHA256(clang+llvm-6.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)=

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

SLES11 binaries for rc3 uploaded. 55b63de8adc12c67eb11abcf1a5f7132cca59b4e clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers < release-testers at lists.llvm.org> wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure

http://prereleases.llvm.org/ On Wed, Jan 24, 2018 at 1:08 PM, Nat! via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On 17.01.2018 18:53, Hans Wennborg via llvm-dev wrote: > >> 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

Dear everyone, The release schedule has snuck up on me again, and it's time to wrap up the release. We won't make it to the final tag on the 21st as per the schedule, but I would like to get all outstanding blockers fixed and rc3 tagged by Friday. Hopefully this would be the last rc and we could go to final soon after. If you're involved in a release-blocking bug (see

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

On 8 February 2016 at 22:56, <cbergstrom at pathscale.com> wrote: > Imho it's critical to get parallel programming working on ARMv8 ( even if it's crappy OMP) to start. Please enable it and I'll run the tests against our internal QA and we can informally handle testing / guarding against regressions. So, I got some dependency errors while building OpenMP on my AArch64 box:

On 8 February 2016 at 22:56, <cbergstrom at pathscale.com> wrote: > Imho it's critical to get parallel programming working on ARMv8 ( even if it's crappy OMP) to start. Please enable it and I'll run the tests against our internal QA and we can informally handle testing / guarding against regressions. Ok, I'll do it with rc3. cheers, --renato

Hello everyone, The release branch for 6.0.0 was created from trunk at r321711 around 3pm GMT today, and the trunk version was subsequently incremented to 7.0.0. (Hopefully the git mirror will have the branch soon too.) Note that this time we're doing an early "slow start" of the release process. I'm still on vacation and there is no release candidate scheduled until 17

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Hello everyone, A little less than a week after rc3, the llvmorg-11.0.0-rc4 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc4 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725

Hello everyone, It took a bit longer than planned, but Release Candidate 3 is now here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at 3a843031a5 and contains 95 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/#rc3 and

Hello everyone, After some delay, the llvmorg-11.0.0-rc3 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc3 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc3 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725 Release testers:

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

On 17.01.2018 18:53, Hans Wennborg via llvm-dev wrote: > 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 Is there a way to

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

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

Hi Dan, You can commit it to ReleaseNotes.rst on the branch directly, or send me a patch or just some text and I'll do it for you. Thanks, Hans On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote: > Hi Hans, > >> To get a change committed to the branch, first commit it to trunk as >> usual, and then request it to be merged --- ideally by filing a