similar to: [LLVMdev] [3.6 Release] Time to fix the release notes

Dear everyone, It's time for the release notes nagging email. We have release notes for LLVM, Clang, clang-tools-extra, lld, and Polly. (If there are more, please let me know.) Most of these are pretty empty files; see e.g. the LLVM one at [1]. The internet does read these notes when we release, so please help make them informative! If you made any interesting changes during the past six

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I

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

Reminder: The plan is to create the 3.6 branch next week, on 14 January. Please help get the release notes and other documents updated. For example, both the LLVM [1] and Clang [2] release notes look pretty empty. Also, if you'd like to volunteer to be a release tester, please let me know. Cheers, Hans 1. http://llvm.org/docs/ReleaseNotes.html 2.

Hello all, Source and binaries for LLVM 3.6.0-rc2 are now available at http://llvm.org/pre-releases/3.6.0/ Please try them out, run tests, build your favourite projects, and *file bugs* about anything that doesn't work or needs to be fixed for the release. Release blockers are tracked by http://llvm.org/PR22374 Cheers, Hans

Hey all, The AVR backend has now finally been merged in-tree completely. Thanks to Krzysztof and Matt for all of their hard work reviewing patches <https://reviews.llvm.org/differential/query/AuHaJ3SXjDmO> Development will now halt on the downstream repository (on GitHub <https://github.com/avr-llvm/llvm>), and it will now be done LLVM proper. This is good news, especially for the

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

On Wed, Aug 26, 2015 at 4:43 PM, Hans Wennborg <hans at chromium.org> wrote: > 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: > > - r245902: Revert r245355: change of clang-tools-extra symlink in the > release script > - r245947: Merge of r245927: Fix LLDB build on MIPS > - r245948: Deprecate the DataLayout on the TargetMachine, and backport > the 3.8 API

Hi, is it possible to have appropriate tags for the Git repositories @ github? I see a Git branch "release_36", but what has v3.6.0rc2 for a commit-id, can you tags that? No, there are no tags at all @ github. Can you add in your announces a svn-trunk revision next time (for rc3)? Somehow it should be clear what is "rc2". Thanks. Regards, - Sedat -

Hi Hans, I have attached a unit test which demonstrates a hang/infinite loop with the opt built with release_36 sources. The fixes are already pushed to "master" branch. The revisions r226588 and r226616 should be pushed to release_36 to fix the unit test. --Sumanth G -------------- next part -------------- An HTML attachment was scrubbed... URL:

cmake ../llvm/ -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_INSTALL_PREFIX=../install -DLLVM_TARGETS_TO_BUILD="XXX" -DLLVM_ENABLE_PROJECTS='lld;clang;' ________________________________ From: Hans Wennborg <hans at chromium.org> Sent: Thursday, March 21, 2019 2:21 AM To: Josh Sharp Cc: Brian Cain; via llvm-dev Subject: Re: [llvm-dev] LLVM 8.0.0

Hi, I don't see the release_36 branch in http://llvm.org/git/llvm.git or in the github mirror https://github.com/llvm-mirror/llvm/branches Is this a mistake, something still to be done, or is it a change from previous releases? -- Quentin -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >> >> Dear testers, >> >> 3.7.0-rc1 was just tagged; please start your testing engines :-) >> >> Upload binaries to the sftp and report your results to this thread. >> >> I'm sorry

On Fri, Aug 3, 2018 at 3:38 PM, <paul.robinson at sony.com> wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit <update to llvm/docs/ReleaseNotes.rst> > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git

Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev: > 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. Hi Hans, I can't build the documentation:

I am pleased to announce that LLVM 11 is now finally available. Get it here: https://releases.llvm.org/download.html#11.0.0 This release is the result of the LLVM community's efforts over the past six months (up to 2e10b7a3 on trunk plus commits up to 176249bd on the release/11.x branch). One highlight is that the Flang Fortran frontend is now part of the release. And as usual, there are

I am pleased to announce that LLVM 11 is now finally available. Get it here: https://releases.llvm.org/download.html#11.0.0 This release is the result of the LLVM community's efforts over the past six months (up to 2e10b7a3 on trunk plus commits up to 176249bd on the release/11.x branch). One highlight is that the Flang Fortran frontend is now part of the release. And as usual, there are

Hi all, I would really like to get a patch into 3.6 for libc++. The patch renames template parameters with the names '_A' and '_V' to longer names. '_A' is frequently defined in ctypes.h and that could cause libc++ to not compile. I'm fairly sure the code was added between 3.5 and 3.6 so that would make this a regression. The patch can be found here:

It is my pleasure to announce that LLVM 3.6 is now available! Get it here: http://llvm.org/releases/ This release contains the work of the LLVM community over the past six months: many many bug fixes, optimization improvements, support for more proposed C++1z features in Clang, better native Windows compatibility, embedding LLVM IR in native object files, Go bindings, and more. For details, see

It is my pleasure to announce that LLVM 3.6 is now available! Get it here: http://llvm.org/releases/ This release contains the work of the LLVM community over the past six months: many many bug fixes, optimization improvements, support for more proposed C++1z features in Clang, better native Windows compatibility, embedding LLVM IR in native object files, Go bindings, and more. For details, see