similar to: [LLVMdev] Cygwin patches for 2.7

How can I do function profiling and BB profiling with current llvm and llvm-gcc4? runtime/libprofile is disabled when using llvm-gcc4, but... is there any alternative to linking with libprofile_rt.so? How can I use llvm-prof? is utils/profile.pl obsolete? Thanks in advance, josem

On Mon, 10 Sep 2007, Jose M. Moya wrote: > How can I do function profiling and BB profiling with current llvm and > llvm-gcc4? > > runtime/libprofile is disabled when using llvm-gcc4, but... is there any > alternative to linking with libprofile_rt.so? > > How can I use llvm-prof? is utils/profile.pl obsolete? The profiling support in LLVM hasn't been used for quite a

El lun, 10-09-2007 a las 11:55 -0700, Chris Lattner escribió: > The profiling support in LLVM hasn't been used for quite a while, so it > may have bitrotted slightly. However, the support should basically work, > so it shouldn't take much to bring it back to life. Thank you, it seems working again with this simple patch: Index: runtime/Makefile

Tanya, This patch at the end of this message is needed for Cygwin and GCC 4.2.x series. I also had to disable 'runtime/libprofile' by including the following in 'runtime/makefile' :- ifeq ($(OS), Cygwin) PARALLEL_DIRS := $(filter-out libprofile, $(PARALLEL_DIRS)) endif There maybe a better fix to make it work. Aaron ---------- Forwarded message ---------- From:

Hello, Here's a tiny patch to the VMKIT tools makefile, that allows you to build VMKIT without both Java and CLI. I'm working on a new bytecode front end so wanted a 'clean' mvm without building to two existing front ends. Currently it still tries to build VMJC even when its told not to build the JNJVM. This patch fixes that. Index: tools/Makefile

Hi Dean, Applies thanks! Out of curiosity, which part of mvm are you using? I guess the GC? Nicolas Dean Calver wrote: > Hello, > > Here's a tiny patch to the VMKIT tools makefile, that allows you to > build VMKIT without both Java and CLI. I'm working on a new bytecode > front end so wanted a 'clean' mvm without building to two existing > front ends.

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

I am getting the following on 'make install' on Cygwin both on debug and release builds :- llvm[3]: Installing Release /home/ang/llvm-coff/bin/llvmc.exe make[3]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc/driver' make[2]: Leaving directory `/home/ang/build/llvm-coff/tools/llvmc' make[1]: Leaving directory `/home/ang/build/llvm-coff/tools' make[1]: Entering

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

Hi, when I try to build libprofile with r80670 (both llvm and llvm-gcc) I get this error: make[1]: Entering directory `.../llvm-svn-debug-obj/runtime/libprofile' llvm[1]: Building Debug Bytecode Archive libprofile_rt.bca (internalize) llvm[1]: Installing Debug Shared Library /nfs/a5/astifter/astifter/llvm/llvm-svn-debug-obj/../llvm-svn-debug-install/lib/libprofile_rt.so 0 llvm-ld

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

This is a new build failure as of today. Does this look familiar to anyone? -bw llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter #1 is wrong! i64 (i8*, i32)* @llvm.objectsize.i64 Intrinsic parameter

My mistake. I needed to update llvm-gcc as well. Sorry for the noise. -bw On Dec 23, 2009, at 3:22 PM, Bill Wendling wrote: > This is a new build failure as of today. Does this look familiar to anyone? > > -bw > > llvm[2]: Compiling CommonProfiling.ll to CommonProfiling.bc for Debug build (bytecode) > Intrinsic parameter #1 is wrong! > i64 (i8*, i32)* @llvm.objectsize.i64

Hello, Bill Wendling wrote: > Before we had buildbots, a random patch would break the system. It > would sometimes take a whole day to determine which patch broke it. I see the buildbots are currently showing no problem on 32-bit linux but I get the following build error with TOT (out-of-source autoconf build): [...] make[1]: Leaving directory `/home/melis/c/llvm-svn-release/tools'

On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: > Hello, > > Bill Wendling wrote: >> Before we had buildbots, a random patch would break the system. It >> would sometimes take a whole day to determine which patch broke it. > I see the buildbots are currently showing no problem on 32-bit linux > but > I get the following build error with TOT (out-of-source autoconf

Jim Grosbach wrote: > > On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: > >> Hello, >> >> Bill Wendling wrote: >>> Before we had buildbots, a random patch would break the system. It >>> would sometimes take a whole day to determine which patch broke it. >> I see the buildbots are currently showing no problem on 32-bit linux >> but >> I

On Aug 31, 2009, at 6:48 AM, Paul Melis wrote: > Paul Melis wrote: >> Jim Grosbach wrote: >>> >>> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >>> >>>> Hello, >>>> >>>> Bill Wendling wrote: >>>>> Before we had buildbots, a random patch would break the system. It >>>>> would sometimes take a