similar to: Get full cmake lines and prepocessed source for a GCC bug report

On Wed, Aug 29, 2018 at 10:14 AM, Hans Wennborg <hans at chromium.org> wrote: > On Wed, Aug 29, 2018 at 9:45 AM, Sedat Dilek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC >> mainatiners want two things... >> >> [ FULL CMAKE LINE ] >> >> How do I

On Wed, Aug 29, 2018 at 9:29 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Wed, Aug 29, 2018 at 7:51 AM, Matthias Klose <doko at debian.org> wrote: >> On 28.08.2018 13:55, Sedat Dilek wrote: >>> On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >>>> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev

Hi, I have not sent yet any bug-reports to llvm-dev but I am seeing this build-failure: ... [574/3685] Building CXX object lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o FAILED: lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS

On 28.08.2018 13:55, Sedat Dilek wrote: > On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> Hi, >>>> >>>>

On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Hi, >> >> I have not sent yet any bug-reports to llvm-dev but I am seeing this >> build-failure: >> >> ... >> [574/3685] Building CXX object >>

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

Hi, while experimenting with llvmlinux on Debian/testing AMD64 I wanted to run some x86-64 ASM tests. I fell over [1] and wanted to run it. So, I cloned clang from Git... $ git clone https://github.com/llvm-mirror/clang.git I looked through some docs where I have seen I need "llvm-lit" or "lit.py". The Debian package llvm-7-tools from <apt.llvm.org> does ship

The simplest way to run a clang test case that I know of is to clone both llvm and clang repos, run all the tests, then run an individual test. IIRC like so: git clone llvm ...... cd llvm/tools git clone clang ..... cd ../../ mkdir build cd build cmake ../llvm ninja check-clang ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c On Sun, May 6, 2018 at 7:10 AM, Sedat Dilek via llvm-dev <

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

On Mon, May 7, 2018 at 10:13 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > ... > > sdi at iniza:~/src/llvm-toolchain/build$ ./bin/llvm-lit -v > ./tools/clang/test/Sema/asm.c > llvm-lit: /home/sdi/src/llvm-toolchain/llvm/utils/lit/lit/llvm/ > config.py:334: > note: using clang: /home/sdi/src/llvm-toolchain/build/bin/clang > -- Testing: 1 tests, 1 threads --

> 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 <mailto: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 tests, then run an individual test. >>

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 tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> [ brutal-snip ] >> ... >>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more >>>

On Mon, May 7, 2018 at 5:19 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > On Mon, May 7, 2018 at 10:13 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> >> ... > > >> >> sdi at iniza:~/src/llvm-toolchain/build$ ./bin/llvm-lit -v >> ./tools/clang/test/Sema/asm.c >> llvm-lit: >>

How big is your project? LTO eats RAM even faster than chrome. For example linking clang with LTO could take 16GB of ram. Have you tried using LTO on your project on that machine, or is it your first time? Piotr On Sat, Jul 23, 2016 at 2:42 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 21, 2016 at 12:01 PM, Sedat Dilek <sedat.dilek at

Try as I might I can't seem to get LLVM to bulid using clang/clang++. No matter what I do it insists on using /usr/bin/cc and /usr/bin/c++ which are gcc. Am I missing something obvious? I vaguely remember some document describing a stage1 compiler built by your old toolchain and a stage2 compiler but I can't find the steps to do that any more. $ CC=/usr/local/bin/clang

On 2/12/2016 9:47 PM, Vince Harron wrote: > Are you building LLDB? Im guessing that is where the failure is I'm building LLVM. The failure in the buildbot happens when compiling HexagonFrameLowering.cpp: ---------- FAILED: C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe /nologo /TP /DWIN32 /D_WINDOWS /W4 -wd4141 -wd4146 -wd4180 -wd4244 -wd4258 -wd4267 -wd4291 -wd4345 -wd4351 -wd4355 -wd4456

Hi, when I switch to an unsupported GCC like v4.6.4 to build LLVM v3.8-rc3 with cmake I get the following: ... -- Looking for __atomic_fetch_add_4 in atomic -- Looking for __atomic_fetch_add_4 in atomic - not found CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first):

> On Jul 23, 2016, at 1:53 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > On Sat, Jul 23, 2016 at 7:48 PM, Piotr Padlewski <prazek at google.com <mailto:prazek at google.com>> wrote: >> How big is your project? >> LTO eats RAM even faster than chrome. For example linking clang with LTO >>

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter