search for: toolchains

On 10/04/2014 16:32, Tom Stellard wrote: > On Wed, Apr 09, 2014 at 06:47:19PM +0200, Sylvestre Ledru wrote: >> Hello, >> >> Trying the 3.4.1 branch, I get following tests failing: >> LLVM :: CodeGen/X86/2009-06-05-VZextByteShort.ll >> LLVM :: CodeGen/X86/fma4-intrinsics-x86_64.ll >> LLVM :: CodeGen/X86/fp-fast.ll >> LLVM ::

Hello, Trying the 3.4.1 branch, I get following tests failing: LLVM :: CodeGen/X86/2009-06-05-VZextByteShort.ll LLVM :: CodeGen/X86/fma4-intrinsics-x86_64.ll LLVM :: CodeGen/X86/fp-fast.ll LLVM :: CodeGen/X86/vec_shift4.ll LLVM :: CodeGen/X86/vshift-4.ll I am testing on a Debian testing 64b. Does it ring a bell? Sylvestre

Hi, I'm getting a returning build failure when building a linux->windows crosscompiler out of LLVM/Clang. Attached is config.log and below is the output of "make VERBOSE=1" llvm[2]: Linking Release executable FileCheck (without symbols) g++ -I/home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/include

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

I am trying to build llvm-2.7 using non-system gcc/binutils. My gcc version is 4.1.2, and binutils is 2.17.50.0.15. I get the following errors `.L2438' referenced in section `.gnu.linkonce.r._ZNK4llvm16DAGTypeLegalizer13getTypeActionENS_3EVTE' of /build/toolchain/src/llvm-2.7/objdir/Release/lib/libLLVMSelectionDAG.a(LegalizeTypes.o): defined in discarded section

Hi, If I configure llvm-gcc 2.6 with --target=mips or --target=mips-elf, I get: c++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -Wno-unused -DTARGET_NAME=\"mips-elf\" -frandom-seed=0 -I. -I. -I/home/foad/toolchain/llvm/llvm-gcc/gcc

Hi Ruben, Try adding a --build=x86_64-gnu-linux option to configure as well. I don't have that configuration locally, so I can't check to be certain, but IIRC, our configure wants all three for a cross compile like this. -Jim On Aug 21, 2011, at 7:19 AM, Ruben Van Boxem wrote: > Hi, > > I'm getting a returning build failure when building a linux->windows >

On Thu, May 13, 2010 at 12:28 PM, john blair <mailtome200420032002 at yahoo.com> wrote: > I am trying to build llvm-2.7 using non-system gcc/binutils. My gcc version is 4.1.2, and binutils is 2.17.50.0.15. I get the following errors That version of gcc is known to have issues building LLVM; see http://llvm.org/docs/GettingStarted.html#brokengcc . Try upgrading your gcc version. -Eli

L.S., I'm currently in the process of creating Debian packages for clang/llvm release 3.9.0. For this I'm using the steps as explained on 'http://apt.llvm.org/building-pkgs.php'. Up until now I have done: $ debcheckout svn://anonscm.debian.org/svn/pkg-llvm/llvm-toolchain/ $ cd llvm-toolchain/branches $ sh 3.9/debian/orig-tar.sh RELEASE_390 final Now, as is explained, I would

I tried building LLVM 2.1 with no real target CPU backends enabled, just the C backend, by hacking the configure script slightly: --- /home/foad/llvm/llvm-2.1/configure 2007-09-17 22:37:52.000000000 +0100 +++ configure 2007-12-13 10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD"

Hi Eli, I tried to build llvm with gcc-4.4.3 and binutils-2.20.1. This time it failed with /build/toolchain/src/llvm-2.7/objdir/Release/bin/tblgen: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /build/toolchain/src/llvm-2.7/objdir/Release/bin/tblgen) make[1]: *** [/build/toolchain/src/llvm-2.7/objdir/lib/VMCore/Release/Intrinsics.gen.tmp] Error 1 make[1]: Leaving

On Mon, May 7, 2018 at 4:03 PM, Amara Emerson <aemerson at apple.com> wrote: > On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the

...(incorrect but common) assumptions that pointers fit into longs. A very few packages will need modifications because they contain declarations which clash with the headers in this toolchain: where we are aware of problems the maintainers have been informed. At DLL level different Windows' toolchains should be compatible: at C level they mostly are but at C++ level they are pretty much incompatible (so that for example GDAL has to be re-compiled for every toolchain: and Rcpp users need to be careful to use only one toolchain for Rcpp and their packages). All the external software previousl...

>From this website: http://llvm.org/builds/ I've installed the LLVM toolchain on 2 Windows machines. One with Visual Studio 2012 and another with Visual Studio 2013. After installing the LLVM toolchain neither machine shows the LLVM option in the Visual Studio project properties pane where you can select which toolchain to use for the project. Am I missing a step somewhere? :) Thanks for

Hi, unfortunately, my build somehow hangs when linking clang binary and my system is in an unusable state. My toolchain is clang-3.8, gold-1.11 and LLVMgold.so from binutils v2.26.1 (both selfmade) and LTO-flag is enabled. My buildsystem uses cmake-3.6.0 and ninja-1.7.1 (both prebuilt). I have 52 last steps left in my 3rd build. My Linux-kernel is v3.13.0-92 from official Ubuntu repositories.

Hi Tobias, I tried to invoke other passes and none of them are available, e.g.: ~/toolchain/install/llvm-3.8/bin/opt -load ~/toolchain/install/llvm-3.8/lib/libPolly.so -polly-cleanup opt: Unknown command line argument '-polly-cleanup'. Try: '/home/fwinter/toolchain/install/llvm-3.8/bin/opt -help' opt: Did you mean '-polly-tiling'? I am just shooting around hoping to

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

Hello, I need to build a CLANG cross compiler for mips-linux-uclibc. To be completely compatible with the target system, I would like it to use linux 2.6.32.54 headers, binutils 2.25, gcc 4.1.2, and uClibc 0.9.30.1 for the gcc toolchain. I have been able to build the GCC toolchain a variety of different ways, but none of these builds can be "dropped in" via clang as a replacement for

[ Please CC me I ma not subcribed to this mailing-list ] [ CC Tom and Hans as LLVM/stable maintainers ] Hi, I want to understand the version handling in LLVM/Clang/LLD. Normally, I build from "release/10.x" Git branch by using the tool tc-build from ClangBuiltLinux project. With "llvm-10.0.1-rc1" Git tag I was able to setup a llvm-toolchain consisting of the projects

pls read the page of http://llvm.org/builds/ : To use the LLVM toolchain from Visual Studio, select a project in Solution Explorer, open its Property Page (Alt+F7 by default), and in the "General" section of "Configuration Properties" change "Platform Toolset" to "LLVM-vs2010" or "LLVM-vs2012". Alternatively, invoke MSBuild with