search for: 3stage

I saw this; http://bb.pgr.jp/builders/clang-3stage-cygwin Not sure, though, r195406 triggered this issue. I am still investigating. I guess it could be reproducible with -target i686-* on other hosts. 2013/11/25 Rafael Espíndola <rafael.espindola at gmail.com>: >> ecc: note: diagnostic msg: /tmp/ARMAsmBackend-265222.cpp &g...

FYI, I just successfully performed a 3-stage bootstrap with stage2/stage3 object file comparison on x86_64-apple-darwin16 for llvm/clang/clang-tools-extra/compiler-rt/libcxx/openmp/polly using our custom fink packaging scripts with the -DLLVM_REVERSE_ITERATION:BOOL=ON cmake option. There were no stage2/stage3 object file comparison failures or test suite regressions. I do have one question

...23:57:52 polly-amd64-linux | 23:29:30 clang-cmake-thumbv7-a15-full-sh | 23:23:52 lldb-windows7-android | 22:15:39 clang-cmake-aarch64-quick | 21:54:32 clang-3stage-ubuntu | 21:39:52 clang-x86-win2008-selfhost | 19:02:47 perf-x86_64-penryn-O3-polly-unprofitable | 18:50:41 perf-x86_64-penryn-O3 | 18:03:53 clang-x64-ninja-win7...

...01:31:56 clang-bpf-build | 01:30:18 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast | 01:29:27 perf-x86_64-penryn-O3-polly-unprofitable | 01:21:23 lldb-x86_64-ubuntu-14.04-buildserver | 01:11:42 clang-3stage-ubuntu | 01:08:59 llvm-hexagon-elf | 00:58:01 lld-x86_64-freebsd | 00:55:20 sanitizer-x86_64-linux-fuzzer | 00:49:46 clang-atom-d525-fedora-rel...

...ots are doing >> a full 3-stage bootstrap with stage2/stage3 file comparison (ala FSF >> gcc)? > Really? From https://llvm.org/svn/llvm-project/zorg/trunk/buildbot/osuosl/master/config/builders.py, it seemed like those where commented out. no? # {'name' : "clang-3stage-ubuntu", # 'slavenames' : ["ps4-buildslave1a"], # 'builddir' : "clang-3stage-ubuntu", # 'factory': ClangLTOBuilder3Stage.get3StageClangLTOBuildFactory( # clean=True, # env=None, # buil...

...-thumbv7-a15 | 02:36:39 clang-cmake-aarch64-quick | 02:30:09 clang-cmake-aarch64-42vma | 02:12:53 lldb-x86_64-ubuntu-14.04-buildserver | 02:02:40 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc49-cxx11 | 01:55:09 clang-3stage-ubuntu | 01:48:54 clang-cuda-build | 01:43:56 sanitizer-ppc64be-linux | 01:43:19 polly-amd64-linux | 01:41:23 clang-hexagon-elf | 01:38:38 lldb-x8...

...bcxxabi-x86_64-linux-ubuntu-cxx11 | 12 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03 | 12 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-asan | 12 | 0 | 0.0 clang-3stage-ubuntu | 15 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-debian-noexceptions | 8 | 0 | 0.0 libcxx-libcxxabi-singlethreaded-x86_64-linux-debian | 8 | 0 | 0.0 libcxx-li...

...bcxxabi-x86_64-linux-ubuntu-cxx1z | 10 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc49-cxx11 | 10 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-msan | 10 | 0 | 0.0 clang-3stage-ubuntu | 1 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-unstable-abi | 10 | 0 | 0.0 libcxx-sphinx-docs | 10 | 0 | 0.0 libomp-cl...

...07:27:18 llvm-mips-linux | 06:45:40 clang-cmake-mips | 06:38:02 perf-x86_64-penryn-O3 | 06:20:14 clang-with-lto-ubuntu | 05:48:35 clang-3stage-ubuntu | 05:28:25 clang-with-thin-lto-ubuntu | 05:16:37 clang-native-arm-lnt | 04:33:53 clang-cmake-aarch64-full | 04:20:01 clang-cmake-armv7-a15-selfho...

...bcxxabi-x86_64-linux-ubuntu-cxx1z | 11 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc49-cxx11 | 10 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-msan | 11 | 0 | 0.0 clang-3stage-ubuntu | 15 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-unstable-abi | 12 | 0 | 0.0 libcxx-sphinx-docs | 12 | 0 | 0.0 libomp-cl...

...bcxxabi-x86_64-linux-ubuntu-cxx11 | 12 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03 | 11 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-ubuntu-asan | 11 | 0 | 0.0 clang-3stage-ubuntu | 7 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-debian-noexceptions | 7 | 0 | 0.0 libcxx-libcxxabi-x86_64-linux-debian | 7 | 0 | 0.0 libcxx-li...

...bcxxabi-libunwind-x86_64-linux-debian | 10 | 0 | 0.0 perf-x86_64-penryn-O3-polly-before-vectorizer-unprofitable | 256 | 0 | 0.0 sanitizer_x86_64-freebsd | 142 | 0 | 0.0 clang-3stage-ubuntu | 10 | 0 | 0.0 clang-x86_64-linux-selfhost-modules-2 | 346 | 0 | 0.0 clang-sphinx-docs | 109 | 0 | 0.0 clang-ppc...

...was_red ------------------------------------------------------------+--------- clang-cuda-build | 91:11:26 clang-ppc64le-linux-multistage | 62:07:22 perf-x86_64-penryn-O3-polly-before-vectorizer-unprofitable | 54:32:40 clang-3stage-ubuntu | 53:57:51 sanitizer-x86_64-linux-autoconf | 45:37:38 sanitizer-x86_64-linux | 42:49:24 clang-x86-windows-msvc2015 | 42:27:27 sanitizer-windows...

> ecc: note: diagnostic msg: /tmp/ARMAsmBackend-265222.cpp > ecc: note: diagnostic msg: /tmp/ARMAsmBackend-265222.sh > ecc: note: diagnostic msg: > > ******************** > The error only occurs for i386. Any ideas? Open a bug report with ARMAsmBackend-265222.cpp and ARMAsmBackend-265222.sh? Cheers, Rafael

As part of my ELLCC project (http://ellcc.org), I build clang/LLVM on my native x86_64 Linux box and then use it to compile itself. For further sanity checking, I then use that copy to cross compile for other targets (arm, armeb, i386, microblaze, mips, mipsel, ppc, and x86_64). After updating to a recent TOT revision, r195452, I get a strange error when cross compiling for the i386:

I have just committed support to llvm-ar for creating thin archives. The idea of thin archives is that they contain just the symbol table and the path to find the original .o files. By locally making thin archives the default I was able to build llvm+lld+clang with them. The total size of the .a files goes from 181,658,164 to 7,116,900 bytes. Is there any way to do that with cmake without having

...mes for, and having CMake construct the appropriate number of build directories and manage building them all through a single top-level configuration and build directory. If you’re skeptical about how doable this is I’d encourage you to look at this bot -> http://lab.llvm.org:8011/builders/clang-3stage-ubuntu <http://lab.llvm.org:8011/builders/clang-3stage-ubuntu>. >> >> That bot does a full 3-stage clang build from a single CMake invocation: >> >> cmake -C ../llvm.src/tools/clang/cmake/caches/3-stage.cmake -GNinja -DLLVM_TARGETS_TO_BUILD=all -DLLVM_BINUTILS_INCDIR...

...mes for, and having CMake construct the appropriate number of build directories and manage building them all through a single top-level configuration and build directory. If you’re skeptical about how doable this is I’d encourage you to look at this bot -> http://lab.llvm.org:8011/builders/clang-3stage-ubuntu. That bot does a full 3-stage clang build from a single CMake invocation: cmake -C ../llvm.src/tools/clang/cmake/caches/3-stage.cmake -GNinja -DLLVM_TARGETS_TO_BUILD=all -DLLVM_BINUTILS_INCDIR=/opt/binutils/include ../llvm.src > So why not run out of tree instead you may ask? > &gt...

On 14 June 2016 at 17:40, Chris Bieneman <beanz at apple.com> wrote: > The problem comes from that fact that generally builds are structured as configure -> build. What we actually need is "configure some" -> "build some" -> "configure some more" -> "build some more" -> repeat until done. Well, GCC has been doing this for years, and

Moving to llvm-dev (I think this has gone a bit further than a patch review discussion) In hindsight I probably should have explained more of my thinking on this with the patch, or done an RFC on llvm-dev to start with. I’l do that now, and answer the questions along the way. I sent a separate email discussing Justin’s patch review feedback. In the build system today there is no strong