search for: bytecode_library

Hi, I compiled LLVM with debug symbols as: ./configure --enable-profiling --enable-assertions --enable-expensive-checks --enable-debug-runtime --enable-debug-symbols make ENABLE_OPTIMIZED=0 But now if I use 'BYTECODE_LIBRARY=1' in my llvm pass Makefile then I get the following warning: /data/ahmad/llvm/llvm31/Makefile.rules:1273: Bytecode libraries require LLVM capable compiler but none is available **** Although I put clang in llvm/tools. This warning doesn't appear when I compile llvm in non-debug mode. Ch...

...e) is organized as a sub-project of LLVM. We compile our run-time libraries into LLVM bitcode files so that their functions can be inter-procedurally inlined and optimized by LLVM (either by llvm-ld or by libLTO). This is simple to do as defining a macro in the Makefile turns this feature on (BYTECODE_LIBRARY=1, IIRC). If you remove this feature, I will most likely have to re-implement it in all of our projects' Makefiles. I may have to update our test suite Makefiles as well. I'm not sure how time consuming that would be, but I'd rather not have to change all of my projects if I don...

...ed as a sub-project of LLVM. >> >> We compile our run-time libraries into LLVM bitcode files so that their functions can be inter-procedurally inlined and optimized by LLVM (either by llvm-ld or by libLTO). This is simple to do as defining a macro in the Makefile turns this feature on (BYTECODE_LIBRARY=1, IIRC). >> >> If you remove this feature, I will most likely have to re-implement it in all of our projects' Makefiles. I may have to update our test suite Makefiles as well. I'm not sure how time consuming that would be, but I'd rather not have to change all of my proje...

...organized as a sub-project of LLVM. > > We compile our run-time libraries into LLVM bitcode files so that their functions can be inter-procedurally inlined and optimized by LLVM (either by llvm-ld or by libLTO). This is simple to do as defining a macro in the Makefile turns this feature on (BYTECODE_LIBRARY=1, IIRC). > > If you remove this feature, I will most likely have to re-implement it in all of our projects' Makefiles. I may have to update our test suite Makefiles as well. I'm not sure how time consuming that would be, but I'd rather not have to change all of my projects if...

...ub-project of LLVM. >>> >>> We compile our run-time libraries into LLVM bitcode files so that their functions can be inter-procedurally inlined and optimized by LLVM (either by llvm-ld or by libLTO). This is simple to do as defining a macro in the Makefile turns this feature on (BYTECODE_LIBRARY=1, IIRC). >>> >>> If you remove this feature, I will most likely have to re-implement it in all of our projects' Makefiles. I may have to update our test suite Makefiles as well. I'm not sure how time consuming that would be, but I'd rather not have to change all of...

...ect of LLVM. >>>> >>>> We compile our run-time libraries into LLVM bitcode files so that their functions can be inter-procedurally inlined and optimized by LLVM (either by llvm-ld or by libLTO). This is simple to do as defining a macro in the Makefile turns this feature on (BYTECODE_LIBRARY=1, IIRC). >>>> >>>> If you remove this feature, I will most likely have to re-implement it in all of our projects' Makefiles. I may have to update our test suite Makefiles as well. I'm not sure how time consuming that would be, but I'd rather not have to change...

On Sep 29, 2011, at 12:53 AM, Speziale Ettore wrote: > Hi, > >> What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? > > First I have compiled llvm/clang compiled with "gcc (Gentoo 4.5.2 p1.1, > pie-0.4.5)

Hi, > What compiler are you using to build with? I've made it default to clang with less looking around for llvm-gcc, so there may be an issue there. What is your configure line? What host are you trying to build on? First I have compiled llvm/clang compiled with "gcc (Gentoo 4.5.2 p1.1, pie-0.4.5) 4.5.2". Then I have installed llvm/clang. They are in the path: $ clang

...RB) $(LIBTOOL) --finish $(DESTDIR)$(libdir) > endif > > -# Does the library want a bytecode version built? > +#--------------------------------------------------------- > +# Bytecode Library Targets: > +# If the user asked for a bytecode library to be built > +# with the BYTECODE_LIBRARY variable, then we provide > +# targets for building them. > +#--------------------------------------------------------- > ifdef BYTECODE_LIBRARY > > ifdef EXPORTED_SYMBOL_LIST > @@ -378,16 +364,16 @@ > endif > endif > > -all:: $(LIBNAME_BC) > +all-local...

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