similar to: [LLVMdev] Compiler error when building LLVM-GCC

Hi, I am new to LLVM and have been trying to get it working on scratchbox (ARM target). When I try to build llvm-2.1, the build freezes with the following output.. /scratchbox/compilers/arm-softfloat-linux-gcc-3.4.4-cs-2005q3-2-glibc-2.3.6/bin/sbox-arm-softfloat-linux-gnu-nm: 'libgcc/./_dvmd_lnx_s.o': No such file mv -f libgcc/./_dvmd_lnx.visT libgcc/./_dvmd_lnx.vis

Duncan Sands dixit: >Can you bootstrap llvm-gcc (configure with --enable-bootstrap)? Nope, probably because it uses the host C++ compiler instead of the one built in stage1 during stage2: /usr/ports/lang/llvm-gcc/w-llvm-gcc4.2-58935-1/llvm-gcc4.2/host-i386-ecce-mirbsd10/prev-gcc/xgcc -B/usr/ports/lang/llvm-gcc/w-llvm-gcc4.2-58935-1/llvm-gcc4.2/host-i386-ecce-mirbsd10/prev-gcc/

g++ -m32 -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings - pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format- attribute -Werror -mdynamic-no-pic -DHAVE_CONFIG_H -Wno-unused - DTARGET_NAME=\"i686-apple-darwin9\" -DNDEBUG -I. -I. -I/tmp/ llvmgcc42.roots/llvmgcc42~obj/src/gcc -I/tmp/llvmgcc42.roots/ llvmgcc42~obj/src/gcc/.

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

I am new to LLVM, and I'm trying to compile llvm and llvm-gcc from subversion on a Solaris10/SPARC machine. I have already tried building llvm-2.4 on this machine, but it failed. I then tried the subversion sources (rev. # 65253 fro llvm and rev#65263 for llvm-gcc) and llvm at least builds correctly ( I however have not tried testing it!). I can execute binaries located in

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) directory structure test   llvm <-- git clone https://github.com/llvm-mirror/llvm     tools       clang <-- git clone https://github.com/llvm-mirror/clang   llvm_build Debug build: clean build, llvm_build is deleted before llvm_build> cmake

Hi, I am trying to build the LLVM suite on a RedHat Enterprise Linux clone (Scientific Linux <https://www.scientificlinux.org/>). In the latest attempt, the build seems to complete without any explicit failures but the `check-all` process fails. Any ideas about what is wrong or suggestions for how to proceed would be much appreciated. This is the current procedure: sudo yum install

>are you setting the optimized tablegen option? LLVM_OPTIMIZED_TABLEGEN is not active - i will try that >In addition, make sure you have plenty of memory i've got only Intel Core 2 Quad CPU Q8300/2.50Ghz and 8GB RAM for testing not much cpu power AND memory Am 19.09.2018 um 11:31 schrieb James Henderson: > Regarding the Debug build taking hours, are you setting the optimized

Hi, I'm try to build llvm on my PC but it failed. I'm using following command, $ cmake -G "Ninja" ../llvm -DCMAKE_INSTALL_PREFIX=prefix=$INSTALL_PATH -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On $ ninja-build -j 2 I have skipped libcxx and libcxxabi package. It shows below error, 00:04:23 [3261/3430] Building CXX object

>because with that generator the CMAKE_BUILD_TYPE variable is ignored >because it is a "multi-configuration target". thanks for the link, is that a bug in the CMake configuration (or better not getting any warning) or is there just documentation missing? so i can use --config Debug or --config Release and get the correct results - i hope that works the build takes hours

Hello, I'm working on a project involving LLVM and keep shifting between the Debug and Release build by assigning different values to CMAKE_BUILD_TYPE in <llvm_build>/CMakeCache.txt and then building it. I wanted to know if this was a safe alternative to re-configuring the build after removing <llvm_build>/CMakeFiles/ and <llvm_build>/CMakeCache.txt. Thanks, Sanjay

Unfortunately, from personal experience, LLVM_PARALLEL_LINK_JOBS appears to have no effect for Visual Studio builds, AND some of the tools linked can take up several GB of RAM, so you'll end up with paging issues. I ended up getting a RAM upgrade in order to sensibly build it (note, I think builds with debug information take more memory than those that don't, and also the clang projects

Tobi, it looks like this code is the problem: for (std::vector<Value *>::iterator PI = Pointers.begin(), PE = Pointers.end(); ;) { Value *V = *PI; if (V->getName().size() == 0) OS << "\"" << *V << "\""; else OS << "\"" << V->getName() <<

Hello, (cc:llvmdev Keeping on the list to get more eyes on the problem and for archival purposes). Configure will be re-run, yes. LLVM includes some tools which need to be built for the host, even when cross compiling (e.g., tblgen). In a cross-build, these are built in the BuiltTools directory and that's where you're seeing configure being re-run. >From the below snippet it appears

I have found that the extremely expensive compile-time overhead comes from the string buffer operation for "INVALID" MACRO in the polly-detect pass. Attached is a hack patch file that simply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for oggen*8.ll, the compile time is reduced from

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

Hi Sebastian, Yes, you have pointed an important reason. If we comment this source code you have listed, then the compile-time overhead for oggenc*8.ll can be reduced from 40.5261 ( 51.2%) to 20.3100 ( 35.7%). I just sent another mail to explain why polly-detect pass leads to significant compile-time overhead. Besides the reason you have pointed, another reason is resulted from those string

On 01/16/2012 01:19 PM, Pieter Custers wrote: > I am new to LLVM and I've a question about the optimization passes and > in particular about the loop transformation passes. I've setup the LLVM > tool-chain with Polly installed. > > The following example is causing problems with me: > http://llvm.org/docs/Passes.html#indvars > > The input is a .c file with the

I am new to LLVM and I've a question about the optimization passes and in particular about the loop transformation passes. I've setup the LLVM tool-chain with Polly installed. The following example is causing problems with me: http://llvm.org/docs/Passes.html#indvars The input is a .c file with the following loops: # 01 Standard, N=100 for (i=0; i<N; i++) b[i] = a[i] + 5; # 02

Hello, I’m trying the following thing: • build and install llvm with mgcc (system compiler) • build and install llvm-gcc with mgcc • build llvm with llvm-gcc • deinstall llvm(old), install llvm(new) • build llvm-gcc with llvm-gcc(old) • deinstall llvm-gcc(old), install llvm-gcc(new) However, I have the problem that the llvm-gcc(new) does not work: after it is compiled, it tries to build libgcc2