similar to: [LLVMdev] LLVM Clang compiling error

I'm unsure why this is failing this week, but when I build for FreeBSD HEAD, I now get a failure to find <stdarg.h>. Very strange. Maybe its missing a -I /usr/include somewhere? [1950/2811] Building CXX object projects/compiler-rt/lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors.cc.o FAILED: /usr/bin/CC -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS

~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc: In function ‘const char* __tsan::ReportTypeString(__tsan::ReportType, __sanitizer::uptr)’: ~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc:95:41: warning: ISO C++ does not allow ?: with omitted middle operand [-Wpedantic] return GetReportHeaderFromTag(tag) ?: "race on external object";

RFC: Generalize means the sanitizers work with memory Overview ======== Currently, LLVM sanitizers, such as Asan and Tsan, are tied to a specific memory model that relies on presence of hardware support for virtual memory. This prevents sanitizers from being used on platforms that lack such support, but otherwise are capable of running sanitized programs. Our research indicates that adding

Hi, I see that ENABLE_WERROR is being set to off (the default value) in the config.log in the llvm build. However on grepping for WERROR in the compiler-rt folder I get the following output: pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep -Rin WERROR * lib/asan/tests/CMakeLists.txt:38: -Werror lib/asan/asan_malloc_mac.cc:253:// This function is currently unused, and we

> > On Aug 30, 2017, at 12:51 AM, Jiri Danek via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > I found https://github.com/google/java-thread-sanitizer, which seems to > be now abandoned. It used to work with ThreadSanitizer v1. Has anybody ever > tried to make it work with the current ThreadSanitizer? > > I gave it a try and bending java-thread-sanitizer to my

On 06/06/2014 02:33, Alexey Samsonov wrote: > Hi Alp, > > This warning should be fixed by r210301. However, consider > investigating why the frame size appears to be that large. I believe > we build this code with GCC as well and have seen no complaints > from its implementation of -Wframe-larger-than. CC'ing in llvmdev. Like Chandler said it could just be due to lack of

Bill, For some reason the llvm-symbolizer tests fail on ppc: http://lab.llvm.org:8011/builders/clang-ppc64le-linux/builds/182/steps/ninja%20check%201/logs/stdio because it can't be started: /home/buildbots/ppc64le-clang-test/clang-ppc64le/stage1/./bin/llvm-symbolizer: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by

Hi Pranav, On Thu, Aug 1, 2013 at 1:54 AM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Hi, > > I see that ENABLE_WERROR is being set to off (the default value) in the > config.log in the llvm build. However on grepping for WERROR in the > compiler-rt folder I get the following output: > > pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep

Dear Alexey, Yes I am sure that the llvm, clang and compiler-rt are synced to the same version. I downloaded them all from git http://llvm.org/docs/GettingStarted.html#git-mirror I think I need compiler-rt for my project but I'll verify it again to see if I can proceed without it. You are correct that compiler-rt is compiled with the just built clang. The complete command that gives an error

yes I think that is correct. I wrote a simple program to print if sizeof(uintptr_t) != sizeof(unsigned char *) and when I compile with gcc -m64 and execute it on a 64-bit host (that is different from the 32-bit laptop on which I originally compiled the program), it says the sizes are not equal. Thanks Pranav On Thu, Aug 1, 2013 at 9:29 AM, Alexey Samsonov <samsonov at google.com> wrote:

I guess there is lots of stuff that you don't care about besides tsan/go that is built and tested during llvm build, and there is no way to selectively disable each one of that. By design. In the long run we need to fix all failures (please file a proper bug). If you are looking for a temporal workaround, then comment it out. I don't what else to suggest. On Tue, Nov 28, 2017 at 9:47 AM,

Hi all, I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but testing fails: ~/wk/LLVM/build_release$ svn info ../llvm/ Path: /home/csabaraduly/wk/LLVM/llvm Working Copy Root Path: /home/csabaraduly/wk/LLVM/llvm URL: https://llvm.org/svn/llvm-project/llvm/trunk Relative URL: ^/llvm/trunk Repository Root: https://llvm.org/svn/llvm-project Repository UUID:

On Thu, Aug 1, 2013 at 5:32 PM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Dear Alexey, > > Yes I am sure that the llvm, clang and compiler-rt are synced to the same > version. I downloaded them all from git > http://llvm.org/docs/GettingStarted.html#git-mirror > I think I need compiler-rt for my project but I'll verify it again to see > if I can proceed

Hi, I'm having this odd problem with being unable to install gcc, this is what I tried and what I'm getting as an error: $ sudo yum install gcc.x86_64 Loaded plugins: security Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package gcc.x86_64 0:4.4.6-4.el6 will be installed --> Processing Dependency: cpp = 4.4.6-4.el6 for package:

Ok, I got. You should install libstdc++44-devel, too. Please try to install gcc44-c++ and libstdc++44-devel. Note: gcc44-c++ depends on gcc44, but gcc44-c++ and libstdc++44-devel are independent each other, at least on my host, CentOS5. ...Takumi 2012/7/15 Sitvanit Ruah <RUAH at il.ibm.com>: > In order to isolate the problem I am now running on a machine whose only > installation

On Tue, Nov 28, 2017 at 12:16 AM, Kostya Serebryany <kcc at google.com> wrote: > +dvyukov > > On Mon, Nov 27, 2017 at 4:56 AM, Csaba Raduly via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but >> testing fails: >> >> ~/wk/LLVM/build_release$

In order to isolate the problem I am now running on a machine whose only installation of gcc/g++ is gcc44, g++44 For this installation I am getting the following error: COMPILE: clang_linux/asan-i386/i386: /gpfs/haifa-p4/00/pincette/sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc /.../sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:19:10: fatal error:

Hello, It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS into account. This is because clang_compile and clang_link_shared functions call the newly-built compiler directly, and they don't add those flags. Using CMAKE_CXX_FLAGS is necessary on systems where the C++11-enabled libstdc++ is installed not in the default location. For example, the CentOS buildbot uses:

I'll take this from the C++ angle; the C rules are not the same, and I'm not confident they give the same answer. On Mon, Aug 11, 2014 at 2:09 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > The access path matters (in some sense), but this is, AFIAK, valid no > matter how you look at it. > > Let's take a look line by line > > #include <stdio.h> >

On Tue, May 29, 2012 at 9:16 PM, Chandler Carruth <chandlerc at google.com>wrote: > > How do I disable that feature? I've tried -fno-builtin and/or >>> -ffreestanding >>> > with no success. >>> clang (as well as gcc) requires that freestanding environment provides >>> memcpy, memmove, memset and memcmp. >>> >>> PS: Consider