similar to: [LLVMdev] ExtraSource Variable in Makefiles

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

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

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: LIBRARYNAME=previrt SHARED_LIBRARY=previrt LINK_COMPONENTS := transformUtils LINK_LIBS_IN_SHARED=1 include $(LEVEL)/Makefile.common LIBS += -lprotobuf CPPFLAGS += -I${HOME}/.root/usr/include -DGOOGLE_PROTOBUF_NO_RTTI LDFLAGS

(cc'ing llvm-dev) Hello Gregory, i just recompiled llvm from scratch, and was able to build the ocaml kaleidoscope bindings. Did you know the llvm's build system already can compile the kaleidoscope tutorials for you? You can run this to build them: make BUILD_EXAMPLES=1 Or just cd into the examples directory in your build directory, and run "make" there. Anyway, I think the

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>

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

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

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

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

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 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 Reid, just a quick note while you're doing this, a while ago I ran into a problem that the standard makefiles weren't building libraries (like, say, a new pass) correctly on OS X - they were being built as shared libraries and not bundles, so they couldn't be loaded with dlopen. The discussion is in the archives if you want more details... I fixed it locally by doing the following

Hi. Here are my patches and makefiles for compiling ogg, vorbis and vorbis-tools on DOS with DJGPP. They can build them from cvs snapshots and need minimal maintainance (even extract source lists from `makefile.am's). Everything seems to work, except one FP exception on encode at middle bitrates (lowest two and highest bitrates don't cause it) - I don't think it's my

Hello, Another question about the more esoteric parts of C. Is there any way to get dragonegg to handle c function aliases or is there a way to get around this? For example, I've got a simple file: int foo(int x) { return x; } extern typeof(foo) foo2 __attribute((alias("foo"))); Compiling with vanilla gcc I end up with two symbols: foo and foo2 which both refer to the same

Hello, I'm trying to link against an archive that has functions implemented in assembly that are used by my program. When I compile these to LLVM bitcode I get a giant module asm section but no LLVM symbols so when llvm-ld links my program against the library, it doesn't include that file (according to the semantics of static linking). Is there some way to tell LLVM that this file is

Hello, I've closed PR106 (use automake) as WONTFIX. I've already delineated the problems with automake in previous posts but as of now, all the automake related stuff has been removed from the repository. In an effort to start making our makefile system better, I've committed changes to Makefile.rules and a few library Makefiles that nearly double the speed of our compilations. I

Hi Duncan, On Wed, Jun 29, 2011 at 11:32 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Gregory, > > > I've tried the LTO options with dragonegg, but I haven't had any luck > getting it > > to work, > > details? > I think this is a misunderstanding on my part about what the dragonegg plugin is supposed to do. I am looking for something that will