search for: wennborgs

The 3.6 release is drawing nearer, but the release notes could still use a lot of improvement: LLVM: https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst Clang: https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst The good news is that they can be updated all the way up until release. If you have a patch for the release notes, commit it directly to the

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

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

On Thu, Jan 30, 2020 at 9:50 AM Tom Stellard <tstellar at redhat.com> wrote: > > On 01/30/2020 05:25 AM, Hans Wennborg via llvm-dev wrote: > > For example, 7984b47401f7f36475619abf2ff02de3b5ff0481 does not seem to > > have made it to any mailing lists. > > > > This makes things harder for me as release manager, as those changes > > are essentially landing

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:

Marshall, you're the owner here. Is this OK to merge? On Sat, Feb 7, 2015 at 8:39 AM, Dimitry Andric <dimitry at andric.com> wrote: > Yes, please. > > -Dimitry > >> On 06 Feb 2015, at 16:07, Eric Fiselier <eric at efcs.ca> wrote: >> >> Hi all, >> >> I would really like to get a patch into 3.6 for libc++. The patch >> renames

With the new signature file I was able to verify, but there was still a bad signature: "gpg: key 0x0FC3042E345AD05D: 1 bad signature" which I highlighted below. Didn't seem to be a problem, but thought I'd point it out. I'd be glad to do additional tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub

On 05/02/2015 18:34, Hans Wennborg wrote: > On Tue, Feb 3, 2015 at 11:47 AM, Hans Wennborg <hans at chromium.org> wrote: >> 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

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

On Mon, Dec 5, 2016 at 12:02 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 5 December 2016 at 19:56, Hans Wennborg <hans at chromium.org> wrote: >> I'd like to avoid 4.1 because of the potential for confusion about >> whether it's a major release (as it would have been under the old >> scheme) or a patch release. > > But if the versioning

After several years as LLVM release manager, I’ve decided to step down as release manager. I recently haven’t been able to focus as much time on LLVM development as I should, and I don’t want the releases to suffer because of that. I’ve enjoyed all of the releases I’ve done. We have a great team of testers. And the community as a whole really helps out so that we can produce a great produce. I my

Could we aim for mid/late January? I'd like our target triple problems to be sorted out for LLVM 3.6 if I can and early-January doesn't leave many working days to get that finished. Especially given that many people take some holiday around Christmas and New Year. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On

That's odd... Have the branch created as usual? On Fri, Jan 13, 2017 at 9:28 AM, Hans Wennborg <hans at chromium.org> wrote: > Oh wait, the branch on the git mirror doesn't look right! > > Anton, can you take a look? The first commit on the branch for llvm is: > > ------------------------------------------------------------------------ > r291843 | hans | 2017-01-12

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

Hello testers, RC4 has just been tagged (at r229782 on the branch). RC3 was disqualified due to an infloop that Duncan reported, and fixed in r229421. That, fixes for a few scary X86 bugs, a GCC5 bootstrap problem (PR22625), and parts of PR22589 is included in RC4. Baring any showstoppers, this release candidate will be promoted to release. Please let me know how it looks and upload binaries

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

Thanks! Added to the release page now. PR44517 is marked as wontfix. Should we re-open it? PR44518 :-( Should we add this to the list or release blockers? On Tue, Aug 11, 2020 at 2:04 PM Diana Picus <diana.picus at linaro.org> wrote: > > Hi, > > Uploaded ARM & AArch64: > a60394b6508a9b66043f221f87eb4e2f5859f918f46e406b2c1e942d50ead7dc >

On 28 Aug 2015, at 20:12, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Aug 27, 2015 at 6:46 PM, Hans Wennborg <hans at chromium.org> wrote: >> I have promoted RC4 to final; 3.7.0 has reached its final state. >> >> Thanks for all your hard work so far. Please build and upload binaries >> with "-final", and let's ship this next

On Wed, Oct 15, 2014 at 1:06 PM, Hans Wennborg <hans at chromium.org> wrote: > On Tue, Oct 14, 2014 at 3:09 PM, Bill Wendling <isanbard at gmail.com> wrote: >> After several years as LLVM release manager, I’ve decided to step down as release manager. I recently haven’t been able to focus as much time on LLVM development as I should, and I don’t want the releases to suffer