search for: enable_profile

I am trying to compile llvm-gcc for an ARm target. I usine the following configure options: /home/tony/llvm/llvm-gcc/configure --prefix=/home/tony/llvm/llvm-gcc-install/ --program-prefix=llvm-arm- --enable-llvm=/home/tony/llvm/llvm-install/ --enable-pic --disable-bootstrap --target=arm-none-linux-gnueabi --enable-languages=c,c++ Then I try to make: make ENABLE_PROFILING=1 ENABLE_OPTIMIZED=1

yue wrote: > hi, > about [LLVMdev] another question > > thanks > > yueqiang One other thing you might want to try is to put your object tree in a directory that is *not* inside of your source tree. Currently, we don't support using separate object trees that are subdirectories of the source tree. In other words: Will work: ========== SRC_ROOT=/home/yue/llvm

Hi, Standard approach to profiling dynamically loaded libraries with gprof doesn't seem to work with LLVM: export LD_PROFILE=Mylib.so export LD_PROFILE_OUTPUT=. make ENABLE_PROFILING=1 // compiling my project opt -load Profile/Mylib.so -options... but no Mylib.so.profile (or gmon.out) is produced. Profiling libc.so.6 usage by "ls -l", however, works fine. Could anyone explain

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

On Nov 6, 2010, at 5:22 PM, tonyg362 wrote: > > I am trying to compile llvm-gcc for an ARm target. I usine the following > configure options: > > /home/tony/llvm/llvm-gcc/configure > --prefix=/home/tony/llvm/llvm-gcc-install/ --program-prefix=llvm-arm- > --enable-llvm=/home/tony/llvm/llvm-install/ --enable-pic --disable-bootstrap > --target=arm-none-linux-gnueabi

On Wed, Jul 09, 2003 at 10:47:14AM -0500, Nicholas Rizzolo wrote: > I'm having a problem with opt. According to the "Writing an LLVM Pass" > tutorial, all I have to do to get the Hello pass to work is: > > cd ${LLVM_HOME}/llvm/lib/Transforms/Hello > gmake > cd $MYTEST > opt -load ${OBJ_ROOT}/lib/Release/libhello.so -hello < something.bc >

Hi, I am a new user to llvm. I have a small question. I am trying to obtain basic block execution frequency for LLVM blocks for mediabench g721 benchmark. I have generated control flow graphs, and instruction mix of the same. however, to obtain runtime profile information, I tried the following. build llvm in PROFILE_ENABLE mode reconfigure path for all the files. run makefile for benchmark

Hi, I am trying to obtain basic block profiles for mediabench g721 benchmark. I have successfully built llvm in profile_enabling mode. Then so as to find out the block execution frequency, I ran the command, analyze encode.out-cbe. It generated gmon.out which I read using gprof. However, I did not get the basic block level execution frequency. Can anybody help me as to how I can extract the basic

Hey guys, I am trying to speed up some of my LLVM/llc passes. Is there a way to use something like gprof on llc? If not, do you guys know anything that I can use to discover which routines of my passes are taking most of the time? thanks, Fernando

Hi, I'm having a problem with opt. According to the "Writing an LLVM Pass" tutorial, all I have to do to get the Hello pass to work is: cd ${LLVM_HOME}/llvm/lib/Transforms/Hello gmake cd $MYTEST opt -load ${OBJ_ROOT}/lib/Release/libhello.so -hello < something.bc > /dev/null First (just as a friendly reminder), someone may want to go back and double check a bunch of

Hi, Does anyone have experience with doing Canadian cross-builds of LLVM compiler? I need some help here... I'm a new with LLVM, so please don't be too harsh on me. I am building LLVM cross-compiler (and as I mentioned I'm doing it via canadian cross-build): Build platform = Linux, Host platform = Windows Target platform = Linux I'm using mingw32 compiler toolchain to

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.

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron