similar to: [LLVMdev] LLVM 3.5 Pre-Reminder

Have you been sleeping poorly worried about the Clang 3.5 release? Well, this may help! The plan right now is to start testing in July with August as the target release month. There isn’t a schedule yet, of course. But it should be a goodly amount of time for all y’all to prepare for the release process. If you have any questions, please let me know. If you’d like to volunteer to be a tester,

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

We had to roll a release candidate 4 for the 3.5 release. It’s up at the normal place: http://llvm.org/pre-releases/3.5 Please test it and report any major bugs you may find. Thanks! -bw

This is a reminder that we will be branching for LLVM 2.9 in one week! 07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011 GMT What this means for you: Please keep a watch on all of your patches going into mainline. And pay close attention to the buildbots and fix any issues quickly. Also, please try to finish up any last minute feature work. While it won't be the

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

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,

Good day! This is just a reminder that branching for the 3.4 release will occur at this time: Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC What this means for you! ------------------------ * Please keep the release notes up to date -- There has been very few commits to them. Please be proactive and update them with any significant feature that was

Hi Bill, I committed a fix already as r355743 [1], and it fixes `test2` as well. I believe we should merge this into 8.0. /Eric [1] https://github.com/llvm/llvm-project/commit/680e865c313a80b6ec329abde61e1f0c66bdc103 On Fri, Mar 8, 2019 at 5:46 PM Bill Wendling <isanbard at gmail.com> wrote: > Hi Eric, > > The attached patch may help matters, though it now fails because

[Adding the correct cfe-dev mailing list address.] On Thu, Jun 27, 2019 at 11:06 AM Bill Wendling <isanbard at gmail.com> wrote: > Now that ASM goto support has landed, Nick Desaulniers and I wrote up a > document describing how to expand clang's implementation of ASM goto to > support output constraints. The work *should* be straight-forward, but as > always will need to

On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > Good day! > > This is just a reminder that branching for the 3.4 release will occur at this time: > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC > > What this means for you! > ------------------------ > > * Please keep the release notes up to date --

The LLVM 3.4rc2 binaries are now available for testing! Please download them and compile and test things. See if it breaks your code! Please file bugs for any issues you encounter. At this point, we’re only accepting fixes for regressions from 3.3. Share and enjoy! -bw

Jack, Where do the "-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.8" flags come from? I don't see them in your CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this being done on purpose? I can add a CMake step checking whether the current CFLAGS/LDFLAGS allow to build an

The LLVM 3.4 branches are now frozen. We’re only accepting major, super horrible bug fixes from now on. The testers are going to do a third phase of testing, but it’s mostly to verify that we don’t have any major problems left. Share and enjoy! -bw

On Tue, Jan 7, 2020 at 5:35 PM Jonas Devlieghere <jonas at devlieghere.com> wrote: > On Tue, Jan 7, 2020 at 5:16 PM Bill Wendling via cfe-dev > <cfe-dev at lists.llvm.org> wrote: > > > > On Tue, Jan 7, 2020 at 4:59 PM Doerfert, Johannes <jdoerfert at anl.gov> > wrote: > >> > >> Hi Bill, > >> > >> On 01/07, Bill Wendling

On Sun, Nov 10, 2013 at 7:50 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > > Good day! > > > > This is just a reminder that branching for the 3.4 release will occur at > this time: > > > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November > 19, 2013 at 3:00:00

Just a reminder that today is the last day for pre-release2 testing. Thanks, Tanya

+grosbach Hi Hal, Re (1): Jim is our resident ARM expert. Adding him here. Re (2): There are a ton of simple programs that have been reported over the last month that are failing at higher levels. It's quite disturbing, really. I don't have a lot of time to debug these (it's no longer my main job to work on LLVM). I'll try to press people as much as possible. -bw On Wed, Dec

On Thu, Jun 27, 2019 at 1:44 PM Bill Wendling <isanbard at gmail.com> wrote: > On Thu, Jun 27, 2019 at 1:29 PM James Y Knight <jyknight at google.com> > wrote: > >> I think this is fine, except that it stops at the point where things >> actually start to get interesting and tricky. >> >> How will you actually handle the flow of values from the callbr

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 Oct 21, 2009, at 3:44 PM, Tanya Lattner wrote: > Just a reminder that today is the last day for pre-release2 testing. > Hi Tanya, Attached are the log files for Mac OS X 10.5.8 on PowerPC. There are these failures for clang: ******************** Failing Tests (20): /Volumes/SandBox/2.6/llvm-2.6/tools/clang/test/CodeGen/ always_inline.c