similar to: [llvm-toolchain v3.8.1] LTO: Linking clang hangs with ld.gold and LLVMgold.so plugin

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

> 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 >>

Hi, I am still struggling with my optimized/speedup build of llvm-toolchain v3.8.1. Here: Enable LTO, PGO, optimized-TableGen, split-DWARF and build with GNU/gold and LLVMgold-plugin. The objcopy (binutils v2.22) here on Ubuntu/precise AMD64 does not support '--extract-dwo'. My build fails with... /usr/bin/objcopy: unrecognized option '--extract-dwo'. Now, I did a full build of

Please have a look at the dedicated mailing list: http://lists.llvm.org/pipermail/llvm-branch-commits/ Please wait for the official release to happen, you will then find tarballs on llvm.org. They will also contain correct version strings, though I haven't yet tried building from the SVN branches directly. Maybe you need to use the SVN tags, $ clang --version currently gives me "clang

The source tarball for clang-tools-extra-3.9.0.src.tar.xz is also missing as well from http://llvm.org/releases/3.8.1/. Jack On Tue, Jul 12, 2016 at 7:34 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > There is no compiler-rt v3.8.1 source tarball available on > <http://llvm.org/releases/3.8.1/>. > > - Sedat - > > On Mon, Jun 27, 2016 at

On Mon, Jun 27, 2016 at 9:12 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>>> What you're probably missing is that 3.8.1 is made in release_38 >>>> branch. So, everything is there and already mirrored. >>>> >>>> Source tarballs will be available upon the release. >>> Which are just coming, now that final has been

On Mon, Jun 27, 2016 at 9:39 AM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-aachen.de> wrote: > Please have a look at the dedicated mailing list: > http://lists.llvm.org/pipermail/llvm-branch-commits/ > OK, I clicked the offline version of that ML on the main-page of <llvm.org>, so I knew of it. Anyway, I think most people use Git these days. > Please wait for the official

>>> What you're probably missing is that 3.8.1 is made in release_38 >>> branch. So, everything is there and already mirrored. >>> >>> Source tarballs will be available upon the release. >> Which are just coming, now that final has been tested successfully. :) >> They'll be announced in the list and available here: >>

On Mon, Jun 27, 2016 at 12:14 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Building with CMake sets the version-string correct whereas using >> autotools as build-system does not. > > Hi Sedat, > > This was reported earlier and it's unfortunate, but we don't support

> Can you answer my question on how to set the version-string correct > when generating tarballs out of the release_38 Git branch? > ( I generated source-tarballs out of my local Git repositories, see below. ) [ llvm.src/CMakeLists.txt ] ... if(NOT DEFINED LLVM_VERSION_MAJOR) set(LLVM_VERSION_MAJOR 3) endif() if(NOT DEFINED LLVM_VERSION_MINOR) set(LLVM_VERSION_MINOR 8) endif() if(NOT

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

On Mon, Jun 27, 2016 at 10:16 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Mon, Jun 27, 2016 at 12:14 PM, Renato Golin <renato.golin at linaro.org> wrote: >> On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>> Building with CMake sets the version-string correct whereas using >>> autotools as build-system

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the

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 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 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: > Building with CMake sets the version-string correct whereas using > autotools as build-system does not. Hi Sedat, This was reported earlier and it's unfortunate, but we don't support autotools build any more. The official releases are made using CMake and most of the buildbots are using it. Feel free

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 Tom, Hi Anton, the first I had in mind was... "Another (LLVM/CLang) realease - a new drama!" ( See Byron Katie "The work". ) I know SVN is your 1st development platform. Personally, I prefer Git and use the LLVM/Clang mirrors on GitHub. Unfortunately, I am missing a "release_381" branch at all on the GitHub repositories. I looked through the llvm-commits [1]

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no

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