similar to: [LLVMdev] llvm-gcc4 & mingw32

Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

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

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

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

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.

On Jan 19, 2009, at 12:35 PM, Dan Villiom Podlaski Christiansen wrote: > On 19 Jan 2009, at 21:16, Mike Stump wrote: > >> On Jan 19, 2009, at 11:55 AM, Dan Villiom Podlaski Christiansen >> wrote: >>> In my humble opinion, using OPTIONAL_DIRS would be better and >>> cleaner. >>> It may require some changes to ‘Makefile.rules’ to work as >>>

Hi, I was trying to write a sample optimization pass in LLVM, by following instructions in LLVM doc for Writing a New Pass. But then ran into *make*issues. The issue is with having separate *source *and *build* directories. The LLVM doc for 'Getting Started' suggests keeping the two separate, but the 'Writing a new pass' doc assumes they are merged. Hence the *make *issue. I did

On Jan 19, 2009, at 11:55 AM, Dan Villiom Podlaski Christiansen wrote: > In my humble opinion, using OPTIONAL_DIRS would be better and cleaner. > It may require some changes to ‘Makefile.rules’ to work as > intended, though. If there's interest in such a change, I can prepare > a patch? Are OPTIONAL_DIRS parallel? For some reason, I was assuming not.

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

Dear list, I'm working with a MySQL-Table and would like to extract selected ids that are stored in a vector: Ids <- c(1,2,3) How do I insert this variable in a for loop like this: For (a in values) { Temp <- dbGetQuery(con, "select * from db Where id = <ID>";) } My problem is to split the select-statement and insert the current id. How can I handle this problem?

Using dovecot 2.0.13. I went to implement relay-ctrl per directions on the Wiki, and failed. After running it down, as best as I can determine, the problem is that the $IP variable is not getting set (and thus not re-set in the script wrapper). I plunked a "set >> debug" into the script, and the only env var's that are set are as listed below (slightly sanitized for public

Hello, I'm trying to modify my r-script to use RODBC instead of DBI/RMySQL (no more ready-to-use package for windows). I would like to copy a data.frame of 44 columns to a table of 45 columns (the 45th is an autoincremental column). With the following commands, colnames(df)<- a vector with the names of the 44 columns

On 19 Jan 2009, at 21:16, Mike Stump wrote: > On Jan 19, 2009, at 11:55 AM, Dan Villiom Podlaski Christiansen wrote: >> In my humble opinion, using OPTIONAL_DIRS would be better and >> cleaner. >> It may require some changes to ‘Makefile.rules’ to work as >> intended, though. If there's interest in such a change, I can prepare >> a patch? > > Are

Hi, I am trying to create a pass that should get statically linked into opt (since I'm on both mac and native win32 and win32 does not support LOADED_MODULEs, at least I get errors while trying to create one). So I have it working with CMake on windows but when I try to run the same code base on mac I get unresolved externals. Here is what I have done so far in the build system: Within

On Oct 3, 2013 11:47 PM, "Rekha R" <rekharamapai at nitc.ac.in> wrote: > > Hi, > > I was trying to write a sample optimization pass in LLVM, by following instructions in LLVM doc for Writing a New Pass. But then ran into make issues. The issue is with having separate source and build directories. The LLVM doc for 'Getting Started' suggests keeping the two

On 9/2/06, Chris Lattner <sabre at nondot.org> wrote: > > Make sure to add it to Codegen/LinkAllCodegenComponents.h. I'm sure I did. I did so from the first time and I also needed to add my library .a file to the USEDLIBS variable within llc makefile to build llc. I wonder how lli links with all the rest LLVM as it seems to include no lib within its makefile. May be I need to

On Sat, 2 Sep 2006, Anton Vayvod wrote: > I'm sure I did. I did so from the first time and I also needed to add my > library .a file to the USEDLIBS variable within llc makefile to build llc. > I wonder how lli links with all the rest LLVM as it seems to include no lib > within its makefile. May be I need to include/link my lib somewhere else? Ah, that's probably it. Try