search for: common_flags

...MacPorts now default to the clang compiler on later darwin. The following change to the dragonegg 3.2 Makefile solves the problem here... --- dragonegg-3.2/Makefile.orig 2012-12-07 12:50:30.000000000 -0500 +++ dragonegg-3.2/Makefile 2012-12-07 12:51:21.000000000 -0500 @@ -42,8 +42,8 @@ else COMMON_FLAGS+=-fvisibility=hidden endif -CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags) -CXXFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cxxflags) +CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags | sed -e 's/-Wcovered-switch-default//') +CXXFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CON...

...r > on later darwin. The following change to the dragonegg 3.2 Makefile solves > the problem here... > > --- dragonegg-3.2/Makefile.orig 2012-12-07 12:50:30.000000000 -0500 > +++ dragonegg-3.2/Makefile 2012-12-07 12:51:21.000000000 -0500 > @@ -42,8 +42,8 @@ > else > COMMON_FLAGS+=-fvisibility=hidden > endif > -CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags) > -CXXFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cxxflags) > +CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags | sed -e 's/-Wcovered-switch-default//') > +CXXFLAGS+=$(COMMON...

...dependency for building >>>> dragonegg. >>>> Jack >>>> -------------- next part -------------- Index: Makefile =================================================================== --- Makefile (revision 169698) +++ Makefile (working copy) @@ -42,8 +42,8 @@ COMMON_FLAGS+=-DENABLE_LLVM_PLUGINS else COMMON_FLAGS+=-fvisibility=hidden endif -CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags) -CXXFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cxxflags) +CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags | sed -e 's/-Wcovered-switch-default//') +C...

Hi Jack, this occurs because you compiled LLVM with clang (right?) and dragonegg is compiled with the same flags used to compile LLVM (it is an llvm-config bug in my opinion that llvm-config output includes these kinds of optional flags). Ciao, Duncan. On 07/12/12 18:11, Jack Howarth wrote: > Duncan, > I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the > compiler

Quick question... asan/msan/tsan all call __sanitizer_set_report_path(common_flags()->log_path), but ubsan does not (which, in practice, seems to mean that you can't redirect the ubsan output anywhere but to the default logging path of stderr). Is there any reason why this can't happen, or it would be a bad idea? Thanks again, Hal -- Hal Finkel Assistant Computation...

Duncan, I am unable to complile dragonegg 3.2 with FSF gcc 4.7 due the the compiler errors... GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config VERBOSE=1 ENABLE_LLVM_PLUGINS=1 make CPPFLAGS="-g -DENABLE_LTO -I/sw/include" /sw/lib/gcc4.7/bin/gcc-4 --version > /dev/null /sw/opt/llvm-3.2/bin/llvm-config --version > /dev/null Compiling utils/TargetInfo.cpp

...quot;hahaha\n"); return 1; } Makefile ==================================================================================== LLVM_CONFIG?=llvm-config # location of the source # useful if you want separate source and object directories. SRC_DIR?=$(PWD) #ifndef VERBOSE # QUIET:=@ #endif COMMON_FLAGS=-Wall -Wextra #-fvisibility=hidden CFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cflags) CXXFLAGS+=$(COMMON_FLAGS) $(shell $(LLVM_CONFIG) --cxxflags) #ifeq ($(shell uname),Darwin) #LOADABLE_MODULE_OPTIONS=-bundle -undefined dynamic_lookup #else LOADABLE_MODULE_OPTIONS=-shared -Wl,-O1 #endif TE...

On Mon, Dec 8, 2014 at 2:00 AM, Alexander Potapenko <glider at google.com> wrote: > Hope you're assuming there's always a single copy of common_flags in > the process. > This isn't the case for e.g. ASan+UBSan on Mac, but that's a broken setup. > > What if we let the tools protect specific flags (by adding a bool to > each flag) once they set their values (when setting the default > values, parsing xSAN_OPTIONS, etc) &g...

Hi all, TL;DR 1) We should change the way we parse common runtime flags in sanitizers. 2) We should make ASan aware of the tools it can be combined with (LSan and UBSan). 3) We may have to restrict the tools UBSan can be combined with (currently to ASan) (see [1]) Currently we have two kinds of sanitizer runtime flags: tool-specific flags and "common flags", defined in sanitizer_common

Hello, I'm quite new to LLVM, but I'm interested in memory sanitizer. The petty thing is, that 32bit addressing on Linux is not supported. Thus I tried to take the latest version of the software and to modify it, using Ubuntu 16.04 as operating system. Given the example example.c: #include <stdio.h> #include <stdlib.h> int main(int argc, char **argv) { int *a = (int