similar to: [LLVMdev] Clang 3.5 Release Pre-Pre-Pre-Announcement

This is just a reminder that the 3.5 release will be starting up in July. Most likely the 2nd week. Details will come later. But you can help things along. * Be sure to update the READMEs! * Try to get your new features in good working condition. * Tackle some of the bugs in the bugzilla. Focus on mis-compilations. * And update the READMEs!! Share and enjoy! -bw

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

The third 3.5 release candidate is now available. Please pick up sources and binaries here: https://llvm.org/pre-release/3.5 Run it through its phases and report any bugs you find! Share and enjoy! -bw

Bill, I have the openmp support in llvm 3.5svn now built on 10.7 using Xcode 4.6.3 and 10.8/10.9 using 5.1.1. The 10.7 build required the hack… perl -pi -e 's|list\(APPEND SANITIZER_COMMON_SUPPORTED_DARWIN_OS iossim\)||g' projects/compiler-rt/CMakeLists.txt to suppress building libclang_rt.asan_iossim_dynamic.dylib. The compiler-rt build now expects the iPhoneSimulator7.0.0.sdk but

Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! What's Expected --------------- You might be asking yourself, "Self, I would like to be an LLVM tester for the 3.3 release, but I don't know what's involved in being one." Well, ask yourself no more! Not only do I have the answers for you, but talking to yourself will cause people to avoid you. Here's

Hi Developers, This is to clarify which patches may be merged into the 3.5 branch. * All doc changes may go in. In fact, you’re encouraged to update the branch's ReleaseNotes.rst file! :-) * All non-documentation patches should first receive approval from the appropriate code maintainer. (A blanket approval is acceptable for the first phase of testing.) * If your patch fixes a major bug,

Hi, I'm pleased to say that my latest attempt at running test-release.sh finished with minor issues (see below) so I'm planning to provide an big-endian MIPS32r2 pre-built binary in the LLVM 3.5 as an experimental/beta release. I was originally hoping to provide little-endian binaries too but I think there's insufficient time remaining for me to get that ready in time for Phase 1

Happy April! [Contrary to the day, this is not an April Fool's joke. ;-)] It has been several months since the release of Clang 3.2. Now is the time to start thinking about the next release! The (very) tentative schedule is testing in May and a release in June. What This Means For You Now is the time to start thinking about which features you are currently working on and getting them

On Mon, Apr 29, 2013 at 01:12:57PM -0700, Bill Wendling wrote: > Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! > Is there an official timeline yet for the 3.3 release? > What's Expected > --------------- > > You might be asking yourself, "Self, I would like to be an LLVM tester for the 3.3 release, but I don't know what's involved in

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

On Dec 15, 2013, at 7:10 PM, C. Bergström <cbergstrom at pathscale.com> wrote: > On 12/16/13 09:57 AM, Bill Wendling wrote: >> On Dec 12, 2013, at 11:08 PM, C. Bergström <cbergstrom at pathscale.com> wrote: >> >>> On 12/13/13 01:58 PM, Bill Wendling wrote: >>>> That’s a long laundry list of bugs there. It would be great to have them fixed, but the

Thanks :-) One last thing. It seems like the patch has a lot of whitespace changes. Could you create the diff with the -b option? -bw On Mon, Jul 7, 2008 at 11:49 AM, Rajika Kumarasiri <rajikacc at gmail.com> wrote: > hi Bill, > Thanks for the comments. I'll update the patch according to that. > > -Rajika > > On Mon, Jul 7, 2008 at 11:56 PM, Bill Wendling

See http://llvm.org/PR19289 for lots of details. It had already been reported before but I had missed it and so had most others. =[ I'm pretty sure this breaks every 32-bit debian based Linux distro. I've asked David Majnemer to try to confirm or refute that. If it does impact every 32-bit debian based Linux distro, I think this should be a release blocker sad as I am to say it. CC-ing

On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } >

On Wed, Jul 15, 2009 at 3:43 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > On Wed, Jul 15, 2009 at 3:01 PM, Bill Wendling<isanbard at gmail.com> wrote: >> The core problem, in my opinion, is that people *don't* pay attention >> to the build bot failure messages that come along. > > That's largely because of the number of false positives. > There

Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there

It is very exciting to see experimental Windows support listed for 3.3. Is there documentation somewhere that tracks what works and what doesn't in this configuration, particularly for C++?. Otherwise it is difficult for those not actively involved in developing Windows support to know what to expect when experimenting. Thanks, Andrew On Mon, Apr 1, 2013 at 5:05 PM, Bill Wendling

We have officially branched for the LLVM 3.4 release!! This means that we are now in the middle of a feature freeze. Here’s what will happen over the next several weeks: * Nov 19 - Nov 24: This is Phase I testing. During this time, you are still able to add code to the release branch. However, you will need to have the approval of the code owner before committing it. We are mostly looking for

> Indeed, dragonegg supports Fortran, but through a gfortran bridge. The > really interesting part in Fortran is in fact arrays! > > Anyway, it's just my opinion, I'm a simple user ;) Fortran has its own standard library and it's damn big. Also, the Fortran grammar is not the simplest (or, rather - straightforward one). So this certainly looks too big for GSoC. Though, it

Hi Tanya, Attached are the "make check" results from my machine Darwin Bill-Wendlings-Computer.local 8.6.0 Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh powerpc I'll have the llvm-test results available later. -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: check.out Type: