similar to: [LLVMdev] [3.3 Release] Help Needed Fixing Bugs

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 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-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

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 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

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

Hi LLVM-inoids, The second phase of testing should have begun already. However, there are still some 3.3 release bugs that are outstanding. See here: http://llvm.org/bugs/show_bug.cgi?id=15999 We need your help in fixing them! Please take a look at them and see if you can jump in an help. Pleaseohpleaseohpleaseohplease! :-) -bw

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

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

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

Hiya! Phase 1 testing of LLVM 3.0 went well. We even found some bugs! These bugs need to be fixed by next Monday so that they can be tested in Phase 2. Please take a look at the umbrella bug report for a listing of regressions: http://llvm.org/bugs/show_bug.cgi?id=11199 Any help would be greatly appreciated! If there are bug fixes you think should go into the release, please contact the code

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 >

Not that I know of but it's definitely something we could use. The basic idea is to use the test-release.sh script that can be found in llvm source tree under utils/release. $ test-release.sh --help usage: test-release.sh -release X.Y -rc NUM [OPTIONS] -release X.Y The release number to test. -rc NUM The pre-release candidate number. -j NUM Number of compile jobs

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

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

On Wed, Mar 9, 2011 at 09:51, Bill Wendling <wendling at apple.com> wrote: > There are LLVM 2.9 RC1 pre-release tarballs source available. You can find > them here: > > http://llvm.org/pre-releases/2.9/ > > Please download them, build them, and compile things to your heart's > content. And most importantly file a bunch of bug reports. :-) > > Share and

+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

The ARM binaries seem to be corrupt. Although correctly signed, the xz file seems to be truncated arm7% unxz < clang+llvm-3.5.0-rc3-armv7a-linux-gnueabihf.tar.xz | wc -c unxz: (stdin): Unexpected end of input 133214381 M.E.O. On Aug 21, 2014, at 10:56 AM, Bill Wendling <isanbard at gmail.com> wrote: > Ahem. And now for the correct URL: > >

Hi Bill, On Fri, Apr 27, 2012 at 12:52:03PM -0700, Bill Wendling wrote: > Hi Wei-Ren Chen, > > Thanks for the reports. Could you ask on the cfe-dev list if adding these flags to the tests are appropriate to fix the issues? > > -bw If I send patch for LLVM 3.1 rc1, what revision I should againt? The one (r154899) which rc1 branch from, or the current svn head? Regards, chenwj