similar to: [3.8 Release] Release Candidate 2 source and binaries available

On 6 February 2016 at 01:02, C Bergström <cfe-dev at lists.llvm.org> wrote: > I worked on the port of llvm-OpenMP-formally-known-as-Intel to Aarch64 > - can it be included there as well? (I'm not sure what's precisely > involved - I'm willing to do my best fixing any bugs which pop up - Hi Chris, That'd entail me enabling them for AArch64. I have to say, I've

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:

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

Dear testers, My list of blockers is empty, and there were no new problems discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. Please build the final binaries and upload to the sftp. For others following along: yes, this means 3.8.0 is complete, but it takes a couple of days to get the source and binary tarballs built. I will send the release announcement when everything's

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

Dear testers, Release Candidate 2 has just been tagged [1]. Please build, test, and upload to the sftp. I know there are still outstanding issues from RC1, but there have been a lot of merges going into the branch and I think it's time for another round of RC testing. This RC comes a little behind schedule, sorry about that, but I'm still optimistic about hitting the target of releasing

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 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

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

According to the schedule (e.g. on the right on llvm.org), we should have tagged the release by now, but we haven't, so we're officially behind schedule. I'm still optimistic that we can wrap this up pretty soon, though. This is what's blocking us: - PR26509: Crash in InnerLoopVectorizer::vectorizeLoop() I'm waiting to hear what Cong comes up with, otherwise we can revert

On Wed, Jun 1, 2016 at 8:52 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "C Bergström" <cbergstrom at pathscale.com> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "cfe-dev" <cfe-dev at lists.llvm.org>, "openmp-dev"

On Wed, Jun 1, 2016 at 11:38 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "C Bergström" <cbergstrom at pathscale.com> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "cfe-dev" <cfe-dev at lists.llvm.org>, "openmp-dev"

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

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch.

On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: >

On 06/05/2018 10:47 AM, Dimitry Andric wrote: > On 4 Jun 2018, at 18:01, Tom Stellard via Release-testers <release-testers at lists.llvm.org> wrote: >> >> The 6.0.1-rc2 release has been tagged. Testers may begin testing and >> reporting results. > > Built for FreeBSD 10, tested and uploaded: > > SHA256 (clang+llvm-6.0.1-rc2-amd64-unknown-freebsd10.tar.xz)

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

I think I did misunderstand what you want to do with attributes. This is my bad. Let me try to explain: It seems you want the "vector-variants" attributes (which I could not find with this name in trunk, correct?) to "remember" what vector versions can be created (wrt. validity), assuming a definition is available? Correct? What I was concerned with is the example I sketched

Dear all, This RFC is a proposal to provide auto-vectorization functionality for user provided vector functions. The proposal is a modification of an RFC that I have sent out a couple of months ago, with the title `[RFC] Re-implementing -fveclib with OpenMP` (see http://lists.llvm.org/pipermail/llvm-dev/2018-December/128426.html). The previous RFC is to be considered abandoned. The original RFC

On 5/30/19 9:05 AM, Doerfert, Johannes wrote: > On 05/29, Finkel, Hal J. via cfe-dev wrote: >> On 5/29/19 1:52 PM, Philip Reames wrote: >>> On 5/28/19 7:55 PM, Finkel, Hal J. wrote: >>>> On 5/28/19 3:31 PM, Philip Reames via cfe-dev wrote: >>>>> I generally like the idea of having support in IR for vectorization of >>>>> custom