similar to: [LLVMdev] LLVM Build Difficulties

Hi Curtis, > I hope this is the right list for such questions.... I've been trying to > get LLVM compiled under Linux (Ubuntu 9.04, 64 bit) for the last couple > of days. I can't reproduce this with ubuntu 9.10, 64 bit x86, gcc 4.4.1, using your configure options. What version of gcc are you using? > CXXFLAGS="-fPIC" ./configure --enable-optimized

On Sep 22, 2009, at 05.11.48, Duncan Sands wrote: > Hi Curtis, > >> I hope this is the right list for such questions.... I've been >> trying to get LLVM compiled under Linux (Ubuntu 9.04, 64 bit) for >> the last couple of days. > > I can't reproduce this with ubuntu 9.10, 64 bit x86, gcc 4.4.1, using > your configure options. What version of gcc are

Óscar, Thanks for the help. I think I'm closer now ... hopefully; although I'm still getting the same error. The "gcc -v" output looks very similar to yours now. Do you see any other obvious configuration issues? I don't know what to try next.... $ ~/Desktop/Build/JamCloud/JamCloudServer$ gcc -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with:

> On May 17, 2016, at 1:33 AM, Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > Let me ask a LTO simple question again. For the llvm LTO example in the link:http://llvm.org/docs/LinkTimeOptimization.html <http://llvm.org/docs/LinkTimeOptimization.html>, I use below build commands to generate three different optimization level binary: -O0, -O1, -O2.

Hi Umesh, Thank you for the suggestion. I can use the "Brute force method " to narrow down the LTO wrong instructions here and there, but I still don't know why these wrong instructions are generated, and how to let Clang LTO don't generate those wrong instructions. I suspect the wrong code is caused by some LTO wrong optimization pass, so I hope to disable all optimizations in

Sorry for not explaining well. After compiling with g++-cross g++-cross -c a.c I do link using this command /gold_binutils/build/gold/ld-new -plugin ~/Desktop/Sanjeev/LLVM/llvm-2.7/Release/lib/libLLVMgold.so --eh-frame-hdr -melf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o /usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0/crtbegin.o

> ~/Desktop/Sanjeev/LLVM/llvm-2.7/Release/lib/libLLVMgold.so --eh-frame-hdr > -melf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o Ok, this way you're generating code for x86 > /usr/lib/crti.o > /usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0/crtbegin.o > -L/usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0  -L/usr/local/lib -lgcc > --as-needed -lgcc_s --no-as-needed -lc -lgcc

Hmm. Odd. I just rebuilt from scratch and it seems to work with the test/CodeGen/X86/xray-attribute-instrumentation.ll test case outputing straight to obj: llc -filetype=obj -o ~/a.o -mtriple=x86_64-apple-macosx < test/CodeGen/X86/xray-attribute-instrumentation.ll What test case are you using? In any case, the issue appears to be that llvm doesn't realize that the target address is

On 6/26/2010 10:30 AM, Rafael Espindola wrote: >> 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 what error is > dlopen reporting. I wonder if gold

> 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

> All the .o files are in the tarball. You can download it here (too large to > send through the list): > http://pages.cs.wisc.edu/~aliang/goldAndDebugTest.tar.gz There is also something strange with these files, buf.o is actually a .tar.gz file :-) > > Thanks, > Guoliang > Cheers, -- Rafael Ávila de Espíndola

On Wed, Jun 22, 2016 at 6:05 AM Nirav Davé <niravd at google.com> wrote: > This appears to work: > > auto Target = OutContext.createLinkerPrivateTempSymbol(); > > with > > auto Target = OutContext.createTempSymbol(); > > -Nirav > > Thanks Nirav -- I tried this but I'm still getting a "jmpq <address>" with this incantation when I load and

On 11 Feb 2015, at 11:16, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > On Wed, Feb 11, 2015 at 12:09 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote: >> On 10/02/15 13:17, Dimitry Andric wrote: >>> On 09 Feb 2015, at 18:52, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> >>>> On Mon, Feb 9, 2015 at 6:44 PM, Emil Velikov

Thanks Nirav, I can confirm that this works when I do the compile with llc, but then when linking to an executable with clang (patched with http://reviews.llvm.org/D20352 and compiler-rt patched with http://reviews.llvm.org/D21612) on Linux, I'm getting something different. Here's a sample of the transcript, and what I'm seeing: --->8 clang invocation 8<--- [16-06-23 3:33:42]

Trunk clang does not pass CMake C Compiler test like below: CMake Error at /home/usr4/c74014i/opt/cmake-3.16.3-Linux-x86_64/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message): The C compiler "/home/usr4/c74014i/opt/clang/current/bin/clang" is not able to compile a simple test program. It fails with the following output: Change Dir:

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

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o

Hi all, I'd like to use LLVM 2.8 on a openSUSE 10.3 box and when I try to compile anything I get an error: martin at vm:~/project/backend> clang tutorial001.m -v -emit-llvm -o tutorial001 clang version 2.9 (trunk 122601) Target: x86_64-unknown-linux-gnu Thread model: posix "/usr/local/llvm/Debug+Asserts/bin/clang" -cc1 -triple x86_64-unknown-linux-gnu -emit-llvm-bc -disable-free

This may be that the libgcc_s.dylib based unwinder is incompatible with the darwin unwinder. You cannot mix and match the two. One of the lines from the bugzilla comments shows: /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, being used. That will not work. All of the libgcc_s.dylib functionality has been subsumed into libSystem.dylib on SnowLeopard (darwin10). The

I realize this is off-topic for the list, but I thought all the darwin developers here might want to be aware of this. The current regressions in gcc trunk regarding exception handling has been escalated to a P1 in order to attract darwin developers to the issue... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260#c31 If these regressions aren't fixed before gcc 4.5's release, it appears