similar to: [LLVMdev] profiling with llvm-gcc4?

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

Hi, Here are two patches to allow Cygwin to build. 'edis' is disabled as it will not build with dynamic libraries, and libprofile also does not build on Cygwin. If anyone using Cygwin wants there functionality they will have to fix them :) Aaron Index: tools/Makefile =================================================================== --- tools/Makefile (revision 97136) +++

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

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

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

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

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

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

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

Hi, Thanks for the replies in the mailing list. I made some progress in building LLVM, but I still have a problem about ELF class. I am working with LLVM on a sparcv9 machine, while the gcc is configured to emit 32-bit binary by default. After executing "configure --with-llvmgccdir=... --enable-jit", I modified Makefile.config so it contains CXX = g++ -mcpu=v9 -m64 CC := gcc -mcpu=v9

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

Good evening, Michael. 2010/9/5 Michael Spencer <bigcheesegs at gmail.com>: > Do you know what the exact problem is? It would be best to fix the > Makefile instead of moving it. And sense it is a transformation, the > build system is broken if you _have_ to move it. I am sorry, I don't understand what *the exact problem" is. I can describe facts; - Hello is the only

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

shouldn't "make distclean" remove include/llvm/Config/config.h ? regards, josem

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.

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 whole day to determine which patch broke it. >>> I see the buildbots are currently

Hi, Zhao > I have checked out llvm 2.9. There is only one CMakeLists file in Release or svn? I believe Nick has committed those CMake files into svn. You can apply my patch to LVM 2.9 Release. > "\llvm-2.9". and no CMakeLists file in folder either > "\llvm-2.9\runtime\libprofile" or "\llvm-2.9\runtime". Where did you get it? As Nick said, libprofile