search for: llvmgccprefix

...llvm-gcc again with -Wl,-debug? This will show the linker > line being used. You can then run gdb on it. Try to find what error is > dlopen reporting. I wonder if gold is calling perror or not when > dlopen fails (assuming it is dlopen that is failing). The -Wl,-debug result is like this: $LLVMGCCPREFIX/lib/gcc/i686-pc-linux-gnu/4.2.1/../../../../i686-pc-linux-gnu/bin/ld -plugin $LLVMGCCPREFIX/libexec/gcc/i686-pc-linux-gnu/4.2.1/libLLVMgold.so -plugin-opt=as=as --eh-frame-hdr -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o $LLVMGCCPREFIX/lib/gcc/i686-pc-linux-gn...

On 6/25/2010 2:37 PM, Rafael Espindola wrote: > The linker (gold) requires you to pass -plugin to it. I am using the command: llvm-gcc a.c -emit-llvm -use-gold-plugin and here is the output: $LLVMGCCPREFIX/lib/gcc/i686-pc-linux-gnu/4.2.1/../../../../i686-pc-linux-gnu/bin/ld: error: $LLVMGCCPREFIX/libexec/gcc/i686-pc-linux-gnu/4.2.1/libLLVMgold.so: could not load plugin library $LLVMGCCPREFIX/lib/gcc/i686-pc-linux-gnu/4.2.1/../../../../i686-pc-linux-gnu/bin/ld: error: /tmp/ccur7bJG.o:1:3: invalid...

> The -Wl,-debug result is like this: > $LLVMGCCPREFIX/lib/gcc/i686-pc-linux-gnu/4.2.1/../../../../i686-pc-linux-gnu/bin/ld > -plugin $LLVMGCCPREFIX/libexec/gcc/i686-pc-linux-gnu/4.2.1/libLLVMgold.so > -plugin-opt=as=as --eh-frame-hdr -m elf_i386 -dynamic-linker > /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o > $LLVMGCCPREFIX/lib/gcc/i...

> Did I use the wrong options? That looks correct, the issues is really why gold is failing to load the plugin. > So the gold and the LLVMgold are linked against the same libstdc++. I am > using the gcc at /s/gcc-4.3.1/i386_rhel5/bin to compile the LLVM chain. Can you run llvm-gcc again with -Wl,-debug? This will show the linker line being used. You can then run gdb on it. Try to find

> So when I copy it to $PREFIX/libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/ and > $PREFIX/lib/bfd-plugins/, should I rename it to libLLVMgold.so? Any other > copies I should make? The copy in that directory can have any name you like. BFD will try all. Note that that is the copy that nm and ar will use. The linker (gold) requires you to pass -plugin to it. >> >> Copying it

On 6/25/2010 8:56 AM, Rafael Espindola wrote: > On 25 June 2010 03:17, Guoliang Jin<jingl1345 at gmail.com> wrote: >> Hi there, >> >> I checked out the latest code from the repository, and wanna use the gold >> plugin, but I got the following: >> >> libLLVMgold.so: could not load plugin library >> >> Do you know why this is happening?

..., and I ported it back to 2.7. The same error happened for both of them: the modified 2.7, and a mainline I checked out three weeks ago. This problem is reproducible while compiling flex-2.5.35.tar.gz and many others (mysql and cherokee). I set the following: export PATH="$LLVMPREFIX/bin:$LLVMGCCPREFIX/bin:$PATH" export CC="llvm-gcc -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" export CXX="llvm-g++ -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" export RANLIB=/bin/true export CFLAGS="-O4 -g" then configure, make, and then hit the error. The error only happ...

On Tue, Jul 20, 2010 at 6:49 AM, Rafael Espindola <espindola at google.com> wrote: >> export PATH="$LLVMPREFIX/bin:$LLVMGCCPREFIX/bin:$PATH" >> export CC="llvm-gcc -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" >> export CXX="llvm-g++ -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" >> export RANLIB=/bin/true >> export CFLAGS="-O4 -g" >> >> then configur...

> export PATH="$LLVMPREFIX/bin:$LLVMGCCPREFIX/bin:$PATH" > export CC="llvm-gcc -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" > export CXX="llvm-g++ -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" > export RANLIB=/bin/true > export CFLAGS="-O4 -g" > > then configure, make, and then hit th...

On Tue, Jul 20, 2010 at 8:49 AM, Rafael Espindola <espindola at google.com>wrote: > > export PATH="$LLVMPREFIX/bin:$LLVMGCCPREFIX/bin:$PATH" > > export CC="llvm-gcc -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" > > export CXX="llvm-g++ -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" > > export RANLIB=/bin/true > > export CFLAGS="-O4 -g" > > > > then co...

On Mon, Jul 19, 2010 at 11:06 PM, Guoliang Jin <jingl1345 at gmail.com> wrote: >  Hi, > > I would like to get the whole program bitcode with debug information in it. > > I tried to use CFLAGS = "-O4 -g", but it ends with the following error: > collect2: ld terminated with signal 6 [Aborted] > Unknown constant! > UNREACHABLE executed at >

On Tue, Jul 20, 2010 at 10:39 AM, Devang Patel <devang.patel at gmail.com> wrote: > On Tue, Jul 20, 2010 at 6:49 AM, Rafael Espindola <espindola at google.com> wrote: >>> export PATH="$LLVMPREFIX/bin:$LLVMGCCPREFIX/bin:$PATH" >>> export CC="llvm-gcc -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" >>> export CXX="llvm-g++ -use-gold-plugin -Wl,-plugin-opt=also-emit-llvm" >>> export RANLIB=/bin/true >>> export CFLAGS="-O4 -g" >>> &g...

Hi, I would like to get the whole program bitcode with debug information in it. I tried to use CFLAGS = "-O4 -g", but it ends with the following error: collect2: ld terminated with signal 6 [Aborted] Unknown constant! UNREACHABLE executed at /local.toadette/aliang/fixing/llvm-2.7/llvm-2.7/lib/Bitcode/Writer/BitcodeWriter.cpp:895! What is the right way to get a whole program bitcode