similar to: [LLVMdev] [3.3 Release] Please: Bug Fixing

On Jun 6, 2013, at 9:04 AM, Hans Wennborg <hans at chromium.org> wrote: > It's probably PR12517. > > Looking at the clang binary, it's got a /home/ dir in RPATH: > > $ objdump -p clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64/bin/clang | grep RPATH > RPATH >

I'm not sure I follow. Will the final binaries have a bad RPATH or not? A 1sec startup pause on some (admittedly crazy) systems seems like a big deal to me. On Fri, Jun 7, 2013 at 6:51 AM, Bill Wendling <wendling at apple.com> wrote: > On Jun 6, 2013, at 9:04 AM, Hans Wennborg <hans at chromium.org> wrote: > > > It's probably PR12517. > > > >

Hi LLVM-ites! We are doing a quick test of 3.3rc3. Our testers did a quick turn around and created binaries which you can test. Please give them a go and let us know how they work for you. They are here: http://llvm.org/pre-releases/3.3/rc3 We don't have a lot of time remaining in the release cycle, so please do whatever you can to make sure they are solid. In particular, make sure that

Hi Bill, I was running some benchmarks and was surprised that the startup performance of your binaries is much worse than the stable binaries for 3.2 I've used: http://llvm.org/releases/3.2/clang+llvm-3.2-x86_64-linux-ubuntu-12.04.tar.gz vs http://llvm.org/pre-releases/3.3/rc3/clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64.tar.gz On a simple hello.c file: /ssd/bench$ TIMEFORMAT="%E"

Hi LLVM-cateers, The first phase of testing is nearing completion. (Actually, it's pretty much done.) You can find binaries here as well as the source code if you want to compile your own binaries: http://llvm.org/pre-releases/3.3/rc1/ We also have several bugs which have been reported. The umbrella bug report is here: http://llvm.org/bugs/show_bug.cgi?id=15999 Now we need your help!

It's probably PR12517. Looking at the clang binary, it's got a /home/ dir in RPATH: $ objdump -p clang+llvm-3.3rc3-Ubuntu-12.04.2-x86_64/bin/clang | grep RPATH RPATH $ORIGIN/../lib:/home/aadgrand/tmp/LLVM-3.3rc3/rc3/Phase3/Release+Asserts/llvmCore-3.3-rc3.obj/Release+Asserts/bin This will slow things down if the system tries to automount /home/aadgrand. Maybe we should merge r182559

Hi! The binaries for the 3.3 release candidate 2 are starting to role in. Please take them and give them a go. Please file bug reports for any problems you encounter. At this point, we are taking fixes only for *serious* regressions from 3.2. I will be pushing back on all requests to merge something into the 3.3 branch. In other words, you will need to do a lot to convince me that we need to go

On May 24, 2013, at 1:19 PM, Bill Wendling <wendling at apple.com> wrote: > Hi! > > The binaries for the 3.3 release candidate 2 are starting to role in. Please take them and give them a go. Please file bug reports for any problems you encounter. > > At this point, we are taking fixes only for *serious* regressions from 3.2. I will be pushing back on all requests to merge

That’s a long laundry list of bugs there. It would be great to have them fixed, but the reality of the situation is that they won’t be fixed for weeks or more, if at all. And with Christmas coming up, it makes things even worse. There are a few days before Phase III starts to have some progress on them. But if they don’t make it, then we’ll have to release without them. -bw On Dec 12, 2013, at

Hi LLVM-ers! The 3.3 release candidate 1 sources are now available! You can get them here: http://llvm.org/pre-releases/3.3/rc1/ Once binaries are available, they will be posted there as well. Please test out these sources and create bug reports for any problems you encounter (http://llvm.org/bugs/) --- and please CC me on those bug reports. Share and enjoy! -bw Note: There are symlinks

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

Bill, et al., There are still a number of open bug reports demonstrating miscompiles on x86 with small/reduced test cases. I propose that we either delay this release until these have been fixed, or plan on a point release in the near future. I recommend that we put out another two release candidates, one at the end of this week, and one after another two weeks or so, to allow for these

Hi all, Phase 1 testing for the 3.1 release is officially over. We did find a few bugs, which we need your help in fixing: http://llvm.org/bugs/show_bug.cgi?id=12568 http://llvm.org/bugs/show_bug.cgi?id=12581 http://llvm.org/bugs/show_bug.cgi?id=12623 Please spend some time investigating these bugs. If you come up with a fix, great! I'll buy you a beer at the next LLVM dev meeting. :-)

Do these need to go into the 3.0 branch? -bw On Oct 25, 2011, at 5:59 PM, Eli Friedman wrote: > 2011/10/25 Török Edwin <edwintorok at gmail.com>: >> Hi, >> >> Looks like the memory_barrier intrinsic got removed in 3.0 and replaced with fence intrinsics. >> Could someone who understands this change better than me please update the 3.0 release notes? >>

On Apr 3, 2013, at 2:07 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 1 April 2013 22:05, Bill Wendling <wendling at apple.com> wrote: > We would like to support ARM again. > > Hi Bill, > > Glad you asked! ;) > > I'm getting the test-suite bot green (a few minor tweaks and we're good) and that should get us well ahead of what we've

Hi LLVM-ites! I wanted to give you a "heads up" on the 3.3 release schedule. Branching [Important] --------------------- We will be branching for the 3.3 release one Monday, May 6th at 5PM PDT (Tuesday, May 7th 12:00 midnight GMT). Tentative Schedule ------------------ The remaining schedule will follow the normal test - bug fix - repeat process: May 6th - 11th --- Phase I

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

The usual procedure is to make time-based releases. So - "release trunk and make sure it's stable enough" plus - fix any outstanding regressions. There is some text wrt this: http://llvm.org/docs/HowToReleaseLLVM.html#release-qualification-criteria On Fri, Dec 13, 2013 at 11:08 AM, "C. Bergström" <cbergstrom at pathscale.com> wrote: > On 12/13/13 01:58 PM, Bill

On Mon, Apr 29, 2013 at 1:12 PM, Bill Wendling <wendling at apple.com> wrote: > 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 >

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