similar to: Updating LICENSE.TXT files

> On Mar 30, 2016, at 1:57 PM, Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > In prepping our next release, we noticed that the LICENSE.TXT files > were still all copyrighted 2015. I've done a bit of archaeology and > it looks like the files to update are: > > cfe/trunk/LICENSE.TXT > clang-tools-extra/trunk/LICENSE.TXT >

On 03/20/2017 03:33 PM, Jonathan Roelofs wrote: > On 3/20/17 1:47 PM, Evandro Menezes via llvm-dev wrote: >> Folks, >> >> I'm at a loss trying to add Compiler-RT to an LLVM build, even after >> checking out the instructions at http://compiler-rt.llvm.org, so I'd >> appreciate your help. >> >> I've tried adding the CMake options

Hi Nelson, Thanks for your reply. The “build/Debug/lib” and "build/Release/lib” directories is where all the libraries go. Similarly, the executables go to “build/Debug/bin” and “build/Release/bin” before they are moved to the install directory. This is expected and normal. However, the problem is that a small number of libraries (exactly 20 in total) are not created at all for the LLVM

All, The following websites will be moving to a new web server in the next few days: clang.llvm.org <http://clang.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> klee.llvm.org <http://klee.llvm.org/> libclc.llvm.org <http://libclc.llvm.org/>

I understand that a difference between ninja and xcode is they use a different way to determine code dependencies. So to my understanding xcode needs dependencies to be properly created whereas ninja just doesn’t care. Maybe this is why ninja is able to find what it needs for the compilation to succeed, but not xcode. So I have now looked at the CMakeLists.txt files and found that all the missing

Try using ninja generator, most people do not use Xcode for building, so since it lesser-used, it also lesser tested. Note that it’s perfectly possible to use Xcode for code browsing, debugging, editing while using ninja for building, which is what I think most people do On Sun, Jul 7, 2019 at 4:20 AM Joan Lluch via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I also filled a bug

I’m not saying you can’t use Xcode, I’m just saying that instead of *building* in Xcode, just type “ninja” on the command line to do your build and then use Xcode as you normally would. I don’t think it’s the case that LLVM does not intend to support Xcode, just that its a community driven project, so unless someone is sufficiently motivated to fix whatever this problem is, it might stay this way

I don’t personally develop on Mac (i use Windows), but I have an analogous setup there where i use ninja to build and Visual Studio for editing, debugging, etc. What i do, and I assume it will be the same or very similar for Xcode, is to run cmake twice, once with Ninja, and once with VS (Xcode for you), from separate directories. I build with the ninja one (“ninja clang” on command line), and I

Hey Joan, Take a look at this patch, and see if it resolves your issue: https://reviews.llvm.org/D64300 <https://reviews.llvm.org/D64300> Thanks, -Chris > On Jul 7, 2019, at 3:54 PM, Chris Bieneman via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hey Joan, > > I looked into the Xcode build issue that you're experiencing, and it relates to a limitation in

Hi we observed that below errors occur on AMD platform since 25de7691a0e27c29c8d783a22373cc265571f5e9 root at lkp-opteron1 /opt/rootfs/llvm_project/src/build# cmake -DCMAKE_BUILD_TYPE=release -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm -DCMAKE_INSTALL_PREFIX=/opt/cross/ -- clang project is enabled -- clang-tools-extra project is disabled -- compiler-rt project is disabled

LKP framework can guarantee that all the software environment are same on AMD and INTEL platform. INTEL platform always work well, after revert this patch, AMD works well. we tried below commit on AMD. 1) 25de7691a0e27c29c8d783a22373cc265571f5e9: bad 2) a82235843b102202766115e10003c9465a8b83ae: good the error logs(build/CMakeFiles/CMakeError.log) has no difference b/w 1) and 2) on AMD platform

Hello everyone, Below are some buildbot numbers for the last week of 6/05/2016 - 6/11/2016. Thanks Galina buildername | was_red -----------------------------------------------------------+----------- sanitizer-x86_64-linux-bootstrap | 134:12:25 perf-x86_64-penryn-O3-polly-parallel-fast | 46:29:26

Hello everyone, Below are some buildbot numbers for the last week of 9/25/2016 - 10/1/2016. Please see the same data in attached csv files: The longest time each builder was red during the last week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed

Hello everyone, Below are some buildbot numbers for the week of 7/10/2016 - 7/16/2016. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

On 05/19/2015 08:50 PM, Chris Matthews wrote: > Just some stats, after looking through lab.llvm.org > <http://lab.llvm.org>:8011 > > Maybe these should be marked as experimental, and removed from the > builders link on the main page. > > Never passed at all: > libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03 > libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan >

On 10/11/2018 03:27 PM, James Y Knight via llvm-dev wrote: > TLDR: https://github.com/llvm-git-prototype/ exists as a read-only mirror of SVN, and is being updated continuously with a script running on an llvm-project AWS VM. > Hi James, What is the current status of the monorepo, have you resolved all the known issues with the history? Are there any other changes that need to be made

On Tue, May 19, 2015 at 10:40 AM, James Y Knight <jyknight at google.com> wrote: > Yes, I also find the amount of bot spam in #llvm is basically intolerable. > It makes it difficult to see actual people talking. At first, I just put > all the bots on /ignore. Now I have an xchat script to move the botspam to > another tab (tabify-004.pl). I'd recommend that the bots should

Folks, I'm at a loss trying to add Compiler-RT to an LLVM build, even after checking out the instructions at http://compiler-rt.llvm.org, so I'd appreciate your help. I've tried adding the CMake options LLVM_ENABLE_PROJECTS, LLVM_BUILD_EXTERNAL_COMPILER_RT, LLVM_EXTERNAL_COMPILER_RT_SOURCE_DIR, CLANG_DEFAULT_RTLIB. All to no avail. FWIW, I'm building for the targets

I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED:

Hello build bot owners! The staging master is ready. Please feel free to use it to make sure your bots would work well with the monorepo and github. The following builders could be configured to build monorepo: * clang-atom-d525-fedora-rel * clang-native-arm-lnt-perf * clang-cmake-armv7-lnt * clang-cmake-armv7-selfhost-neon * clang-cmake-armv7-quick * clang-cmake-armv7-global-isel *