search for: aadgrand

Displaying 6 results from an estimated 6 matches for "aadgrand".

2013 Jun 06
5
[LLVMdev] [cfe-dev] [3.3 Release] 3.3rc3 Now Available
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 to the release branch? Or at least we should take care not to build it in a /home directory. - Hans On T...
2013 Jun 07
0
[LLVMdev] [cfe-dev] [3.3 Release] 3.3rc3 Now Available
...13, 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 > $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 to the release branch? Or at least we > should take care not to build it in a /home...
2013 Jun 07
2
[LLVMdev] [cfe-dev] [3.3 Release] 3.3rc3 Now Available
...ium.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 > > > $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 to the release branch? Or at least we > > should take care...
2013 Jun 07
0
[LLVMdev] [cfe-dev] [3.3 Release] 3.3rc3 Now Available
On 06/06/2013 18:04, Hans Wennborg 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 > $ORIGIN/../lib:/home/aadgrand/tmp/LLVM-3.3rc3/rc3/Phase3/Release+Asserts/llvmCore-3.3-rc3.obj/Release+Asserts/bin To avoid such behavior [1] , in Debian and Ubuntu packages, I am doing: chrpath -d $(TARGET_BUILD)/Release/bin/clang chrpath -d `find $(CURDIR)/debian/tmp/usr/lib/llvm-$(LLVM_VERSION)/bin/ -type f -executable` Syl...
2013 Jun 06
0
[LLVMdev] [cfe-dev] [3.3 Release] 3.3rc3 Now Available
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"
2013 Jun 04
2
[LLVMdev] [3.3 Release] 3.3rc3 Now Available
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