similar to: [LLVMdev] Makefile Question

I thought it would, but it seems to be missing the CloneModule symbol (which isn't called from anywhere in the LLVM codebase). On Fri, Jul 15, 2011 at 7:43 AM, John Criswell <criswell at illinois.edu>wrote: > On 7/14/11 7:36 PM, Gregory Malecha wrote: > > Hello, > > I have a question about how to set up a Makefile that generate a .so that I > can load into opt

On 7/14/11 7:36 PM, Gregory Malecha wrote: > Hello, > > I have a question about how to set up a Makefile that generate a .so > that I can load into opt without getting duplicate symbols. Here's > what I have right now: Have you tried removing LINK_COMPONENTS below? I suspect that the opt binary already contains everying in the transformUtils library. -- John T. > >

Hi Gregory, I had a similar problem a while back, see: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-June/032508.html for my solution to this problem. Basically I ended up linking in the *.o files needed to get exactly what I needed (in your case, the file defining CloneModule and whatever else you need), without pulling in too much (causing duplicate symbol issues with opt). Hopefully this

Hello, I'm interested in the OCaml bindings, but I've been digging through them and it doesn't seem possible to actually write a transformation with them. Specifically, there are a lot of functions to build each type of instruction, but there doesn't seem to be any way to query an llvalue and determine what kind of instruction it is. Is there something that I am missing? Thank

Hello, I'm wondering if anyone had any success (even a small amount) compiling any variant of libc to llvm bitcode? -- gregory malecha -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110622/b5fad437/attachment.html>

On Mon, Jun 13, 2011 at 12:09 PM, Gregory Malecha <gmalecha at gmail.com> wrote: > Hello, Hello Gregory, > I'm interested in the OCaml bindings, but I've been digging through them and > it doesn't seem possible to actually write a transformation with them. > Specifically, there are a lot of functions to build each type of > instruction, but there doesn't seem

Hello, I'm working on a project that involves archive files and since llvm-link does not currently support them, I have a simple patch (attached) to add this functionality. It isn't really efficient (it recomputes the set of symbols that need to be linked in after each link), and it probably has some problems with append linkage, but so far it has been enough for me. I'd like to

On 2011-07-29 16:16, Gregory Malecha wrote: > Hello, > > I'm working on a project that involves archive files and since llvm-link > does not currently support them, I have a simple patch (attached) to add > this functionality. It isn't really efficient (it recomputes the set of > symbols that need to be linked in after each link), and it probably has > some problems

Hello, I'm looking at compiling some pieces of the standard library with llvm but I'm running into problems with some functions being renamed by dragonegg. For example, when I compile the acos implementation with plain gcc I get: $ nm acos.o 0000000000000000 r .LC1 0000000000000048 r .LC10 0000000000000050 r .LC11 0000000000000058 r .LC12 0000000000000060 r .LC13 0000000000000068 r .LC14

Hi Xi, How did you compile it with clang? I ran into problems: clang -emit-llvm -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" -DPACKAGE_VERSION=\"1.19.0\" -DPACKAGE_STRING=\"newlib\ 1.19.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -I. -DMISSING_SYSCALL_NAMES -fno-builtin -DMISSING_SYSCALL_NAMES -fno-builtin -O2 -c -o

Hi Duncan, Ah, non-unicode email... In the llvm output there should be a "1" character, i.e. (char) 0x01, prepended to acos and __GI_acos. I'm unable to get it on smaller things, but it happens when I try to compile uClibc with llvm. I've attached the .o and the .bc for comparison. The text file is the result after preprocessing (to avoid having to download a bunch of stuff).

Hi Gregory, > Ah, non-unicode email... In the llvm output there should be a "1" character, > i.e. (char) 0x01, prepended to acos and __GI_acos. I'm unable to get it on > smaller things, but it happens when I try to compile uClibc with llvm. I've > attached the .o and the .bc for comparison. The text file is the result after > preprocessing (to avoid having to

On Sun, Jul 31, 2011 at 12:43 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Rafael, > >>> I'm working on a project that involves archive files and since llvm-link >>> does not currently support them, I have a simple patch (attached) to add >>> this functionality. It isn't really efficient (it recomputes the set of >>> symbols that need

Hi Rafael, >> I'm working on a project that involves archive files and since llvm-link >> does not currently support them, I have a simple patch (attached) to add >> this functionality. It isn't really efficient (it recomputes the set of >> symbols that need to be linked in after each link), and it probably has >> some problems with append linkage, but so far

Hi Gregory, > I'm looking at compiling some pieces of the standard library with llvm but I'm > running into problems with some functions being renamed by dragonegg. For > example, when I compile the acos implementation with plain gcc I get: > > $ nm acos.o > 0000000000000000 r .LC1 > 0000000000000048 r .LC10 > 0000000000000050 r .LC11 > 0000000000000058 r .LC12

Hi,      I am interested in getting llvm IR only for a subset of the input source code - basically starting from a specified top level function, including all its callee functions (recursively).      For example, in the following code, I am interested in a command like "extract -top_function blah()" that will create an llvm IR with just blah() and foo().       int foo() {          

Hello all, I am trying to port the package RProtoBuf to windows. The developers of RProtoBuf have given me some helpful pointers so far, but now I am stuck. After having made what I think are the necessary changes to the package to compile on windows, "R CMD build RProtoBuf" outputs a somewhat cryptic error ("This application has requested the Runtime to terminate it in an unusual

Hi!! It's me again. I guess that there is a problem in the Makefile of my source code. But I don't know where. Could you please verify it? The Makefile is written like this: # Makefile for Genetic Algorithm Pass CXXFLAGS = -Wall -I/iss/fpga3/nicole/galib247/ LDFLAGS= -L/iss/fpga3/nicole/galib247/ga/ -lga -Wl,-E # Path to top level of LLVM heirarchy LEVEL=../../../ # Name of the

For my application it is important that I get bit code out the other end and I couldn't get the linux linker to link llvm. Is there a way to do this with other tools? I noticed a TODO in the llvm-link.cpp file that said that this should be done so I figured that that would be the right place to do it. 2011/7/30 Rafael Ávila de Espíndola <rafael.espindola at gmail.com> > On

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load