search for: asserts

llvm[4]: Compiling PoolAllocate.cpp for Release+Asserts build /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp: In member function ‘virtual bool llvm::PoolAllocate::runOnModule(llvm::Module&)’: /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp:403:16: error: ‘class llvm::Constant...

...2be/build/'{}' \; |& tee foo.txt Is anyone else doing this? There 2 compilers, recurse 2 and recurse3 that in principle should be identical. Obviously if there is date and time information, miscompares can occur. -------------- next part -------------- ./tools/clang/lib/AST/Release+Asserts/ASTDumper.o ../../recurse2be/build/./tools/clang/lib/AST/Release+Asserts/ASTDumper.o differ: byte 181746, line 385 ./tools/clang/lib/AST/Release+Asserts/AttrImpl.o ../../recurse2be/build/./tools/clang/lib/AST/Release+Asserts/AttrImpl.o differ: byte 192192, line 83 ./tools/clang/lib/AST/Release+Asse...

...-D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fno-exceptions -fno-rtti -fPIC -Woverloaded-virtual -Wcast-qual -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -g -Wl,-R -Wl,'$ORIGIN/../lib' -Wl,-R -Wl,/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/Debug+Asserts/bin -L/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/Debug+Asserts/lib -L/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/Debug+Asserts/lib -o /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/Debug+Asserts/bin/opt /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts...

Bugs item #11183, was opened at 2007-05-28 10:28 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=11183&group_id=35 Category: Incorrect behavior Group: current Status: Open Resolution: None Priority: 3 Submitted By: Patrick McDonnell (kc9ddi) Assigned to: Kevin Smith (qualitycode) Summary: GLib errors cause crash Initial Comment: Hi - I''m

It will be used for the OCaml unit tests. --- configure.ac | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/configure.ac b/configure.ac index e0fb481..e360bbb 100644 --- a/configure.ac +++ b/configure.ac @@ -1120,6 +1120,7 @@ AS_IF([test "x$OCAMLC" != "xno"],[ ]) OCAML_PKG_gettext=no +OCAML_PKG_oUnit=no AS_IF([test "x$OCAMLC" != "xno"],[ #

...s config.status: executing lib/sample/Makefile commands config.status: executing tools/Makefile commands config.status: executing tools/sample/Makefile commands num_cpu=$(echo `sysctl -n hw.ncpu`) echo `sysctl -n hw.ncpu` sysctl -n hw.ncpu make -j $num_cpu llvm[1]: Compiling Alarm.cpp for Release+Asserts build llvm[1]: Compiling Atomic.cpp for Release+Asserts build llvm[1]: Compiling Disassembler.cpp for Release+Asserts build llvm[1]: Compiling DynamicLibrary.cpp for Release+Asserts build llvm[1]: Compiling Host.cpp for Release+Asserts build llvm[1]: Compiling Errno.cpp for Release+Asserts build ll...

...mple/Makefile commands > config.status: executing tools/Makefile commands > config.status: executing tools/sample/Makefile commands > num_cpu=$(echo `sysctl -n hw.ncpu`) > echo `sysctl -n hw.ncpu` > sysctl -n hw.ncpu > make -j $num_cpu > llvm[1]: Compiling Alarm.cpp for Release+Asserts build > llvm[1]: Compiling Atomic.cpp for Release+Asserts build > llvm[1]: Compiling Disassembler.cpp for Release+Asserts build > llvm[1]: Compiling DynamicLibrary.cpp for Release+Asserts build > llvm[1]: Compiling Host.cpp for Release+Asserts build > llvm[1]: Compiling Errno.cpp for...

...LLVM that #ifndef NDEBUG is used as a guard for non-assert code that we want enabled in debug builds. This works fine on its own, however it affects the behaviour of LLVM_ENABLE_ASSERTIONS; since NDEBUG controls whether assertions are enabled or not, a lot of debug code gets enabled in addition to asserts if you specify this flag. This goes contrary to the name of the flag I believe also its intention. Specifically in Flang we have a case where someone wants to ship a build with assertions enabled, but doesn't want to drag in all the extra things that are controlled by NDEBUG in LLVM. In my opi...

Covert common_utils_tests to use oUnit as testing framework, replacing the hand-made assert in favour of structured unit tests and better error reporting. common_utils_tests is now built only when the oUnit module has been found. --- mllib/Makefile.am | 17 ++++- mllib/common_utils_tests.ml | 155 +++++++++++++++++++++++++++----------------- 2 files changed, 108 insertions(+), 64

Hi, The dovecot 2.3.0.1 Debian package currently fails to build on all big-endian architectures[1], due to murmurhash3 tests failing. The relevant output from e.g. s390x is: test-murmurhash3.c:22: Assert(#8) failed: memcmp(result, vectors[i].result, sizeof(result)) == 0 test-murmurhash3.c:22: Assert(#11) failed: memcmp(result, vectors[i].result, sizeof(result)) == 0 test-murmurhash3.c:22:

Hi all, After updating llvm+clang to r174701 by issuing make -j8 happiness The build fails with: ... make[2]: Entering directory `/local/csaba/LLVM/build-release/tools/llvm-diff' llvm[2]: Compiling DiffConsumer.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable lli (without symbols) llvm[2]: Compiling CrashDebugger.cpp for Release+Asserts build /local/csaba/LLVM/build-release/tools/llc/Release+Asserts/llc.o: In function `main': llc.cpp:(.text+0x5119): undefined reference to `LLVMInitializeAArch64Target...

On Wed, Dec 20, 2017 at 04:13:16PM +0000, Wang, Wei W wrote: > On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: > > unsigned long bit; > > xb_preload(GFP_KERNEL); > > xb_set_bit(xb, 700); > > xb_preload_end(); > > bit = xb_find_set(xb, ULONG_MAX, 0); > > assert(bit == 700); > > This above test will result in "!node with bitmap

On 6/27/19 5:07 AM, Martin Kletzander wrote: > This just defines the namespace, its contexts and related constants and the only > supported one is currently base:allocation. The names of the constants are not > very future-proof, but shorter than LIBNBD_META_NS_CONTEXT_BASE_ALLOCATION or > similar. > > Currently the output looks like this: > > /* "base"

...t; > > > As far as I can tell, as it currently works, LLVM_ENABLE_ASSERTIONS > just makes sure that NDEBUG is not defined, even in release builds. So if I > do -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=TRUE, I’ll get an > optimized build with no debug symbols but with asserts enabled, which in my > mind isn’t a terribly useful thing to have. > FWIW, I believe quite a few people use that mode & don't use debuggers much - faster link/compile times, etc. > Furthermore, none of this works on Visual Studio because it has a UI menu > to control the buil...

Currently LLVM releases, as downloaded from llvm.org, have assertions enabled. (I'm told Apple ships LLVM with assertions disabled, which is why I mention llvm.org here). What do people think of disabling assertions? The advantage of disabling assertions is that LLVM runs faster. I don't know how much faster. It also makes for fairer comparisons with gcc releases, which have all but

...say was that it worked for me on OS X on a slightly older > version of LLVM. Anyway, here's the ld line: > > "/usr/bin/ld" -export-dynamic -z relro --hash-style=gnu --build-id > --eh-frame-hdr -m elf_x86_64 -shared -o > /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib/ > libLLVM-3.5svn.so/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crti.o > /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginS.o > -L/home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib > -L/home/kfischer/julia/deps/llv...

Actually it only link the shlib fine. Linking any executable against it fails: llvm[2]: Linking Release+Asserts executable llvm-lto (without symbols) /home/kfischer/julia/deps/llvm-svn/build_Release+Asserts/Release+Asserts/bin/clang++ -fsanitize=address -O3 -Wl,-R -Wl,'$ORIGIN/../lib' -L/home/kfischer/julia/deps/llvm-svn/build_Release+Asserts+Sanitize/Release+Asserts/lib -L/home/kfischer/julia/deps/l...

On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: > On Wed, Dec 20, 2017 at 06:34:36PM +0800, Wei Wang wrote: > > On 12/19/2017 10:05 PM, Tetsuo Handa wrote: > > > I think xb_find_set() has a bug in !node path. > > > > I think we can probably remove the "!node" path for now. It would be > > good to get the fundamental part in first, and

On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: > On Wed, Dec 20, 2017 at 06:34:36PM +0800, Wei Wang wrote: > > On 12/19/2017 10:05 PM, Tetsuo Handa wrote: > > > I think xb_find_set() has a bug in !node path. > > > > I think we can probably remove the "!node" path for now. It would be > > good to get the fundamental part in first, and

Hi, On Linux I observed [root at localhost poolalloc]# find . -name *.a ./Release+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT ~/SAFECode/...