similar to: [5.0.0 Release] Please write release notes

Thanks! r311738. On Thu, Aug 24, 2017 at 4:51 PM, Adam Nemet <anemet at apple.com> wrote: > Hi Hans, > > Opt-viewer is now installed rather than being an internal-only tool so here it goes: > > A new tool opt-viewer.py has been added to visualize optimization remarks in HTML. The tool processes the YAML files produced by clang with the -fsave-optimization-record option. >

I'm sorry, but I don't think LLDB has any release notes. On Sat, Aug 26, 2017 at 9:49 PM, Kamil Rytarowski <n54 at gmx.com> wrote: > LLDB: > > Switched the NetBSD platform to new remote tracing capable framework. > > Preliminary support for tracing NetBSD(/amd64) processes and core files > with a single thread. > > On 25.08.2017 02:44, Hans Wennborg via

Dear everyone, The release branch was recently created from trunk at r308441 and the trunk version was subsequently incremented to 6.0.0. Release blockers are tracked by https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help out with the release by notifying me of any bugs, commits, or other

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

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

Hi, I'm new to llvm and am trying to run benchmarks from the test-suite using lnt to check loop-vectorization for various benchmarks. Test are compiling and executing fine, but I am not getting optimization remarks while using flags like -Rpass-missed=loop-vectorize and -Rpass-analysis=loop-vectorize I've tried running it like this: lnt runtest test-suite --sandbox SANDBOX --cc

On 2017-12-30 21:27, Anton Korobeynikov via llvm-dev wrote: > Hello > > We are not planning to use git tags there (at least until the git > migration would happen). Please use the release branches. To me it doesn't matter if it's a tag or a branch, but, as far as I can see, there are no branches for point releases. For example, there's a branch release_50, but no branch

Hello everyone, With the release drawing near, it would be great to get the release notes into better shape. You can see the notes from rc2 online here: https://prereleases.llvm.org/11.0.0/#rc2 The release notes are typically the first thing people look at after the release, so it's a great opportunity to highlight the work that's been done since the last release. If you can think of

Thanks! Committed in 158581772fc8f3d6c601ceba14a08285e46cb7e9 On Tue, Sep 15, 2020 at 4:23 PM Ahsan Saghir <saghir.ibm at gmail.com> wrote: > > Hi Hans, > Here are the PowerPC release notes for 11.0.0: > > Optimization: > > Improved Loop Unroll-and-Jam legality checks, allowing it to handle more than two level loop nests > Improved Loop Unroll to be able

Committed to 11.x as b6efbd6b5f22d0a251d2fba9a5d24ac21760b1cc. Thanks! On Thu, Oct 1, 2020 at 3:29 AM Lang Hames <lhames at gmail.com> wrote: > > Hi Hans, > > Apologies if I got here too late, but just in case I didn't here are some JIT release notes for 11.0.0: > > - LLJIT now supports execution of static inits / deinits via the LLJIT::initialize and

Dear everyone, We're getting close to the 6.0.0 release, but the release notes are still in a pretty bad state. You can see the notes for rc2 here: http://prereleases.llvm.org/6.0.0/#rc2 (a few things have been added since). When the release happens, a lot of people will look at the notes, so it's a good opportunity to mention the work that's happened in the past six months. If you

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'

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

Thanks for writing this up. I think it's a really important point which deserves discussion. Ultimately, I think it is a question as to whether to prioritize the easy switchover for existing out of tree forks, or to prioritize having the best conversion we can make. I feel very strongly that the latter should be the priority for the official repository conversion, and that, therefore, we

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

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

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:

Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small

On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis <Simon.Dardis at imgtec.com> wrote: > Currently I'm getting "Couldn't write to remote file "/home/testers/uploads/clang+llvm-5.0.0-rc1-mips-linux-gnu.tar.xz": Failure", > does that account need more space? Yes, the partition is full. I've asked Anton to see if we can fix this.