HomeSort by: relevance | last modified time | path
    Searched refs:violations (Results 1 - 4 of 4) sorted by relevancy

  /src/external/bsd/libc++/dist/libcxxrt/test/
test_exception.cc 187 static int violations = 0; variable
190 violations++;
338 TEST(violations == 1, "Exactly one exception spec violation");
  /src/external/gpl3/gcc/dist/libgcc/
unwind-dw2-fde.c 623 unsigned violations = 0;
638 violations += ptrs[j + 1] < ptrs[j];
645 if (!violations)
621 unsigned violations = 0; local
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/scripts/
cpplint.py 1765 Additionally, check for constructor/destructor style violations and reference
  /src/sys/external/isc/libsodium/dist/
configure 8717 { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether segmentation violations can be caught when using the C compiler" >&5
8718 $as_echo_n "checking whether segmentation violations can be caught when using the C compiler... " >&6; }
8772 { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: On this platform, segmentation violations cannot be caught using signal handlers. This is expected if you enabled a tool such as Address Sanitizer (-fsanitize=address), but be aware that using Address Sanitizer may also significantly reduce performance." >&5
8773 $as_echo "$as_me: WARNING: On this platform, segmentation violations cannot be caught using signal handlers. This is expected if you enabled a tool such as Address Sanitizer (-fsanitize=address), but be aware that using Address Sanitizer may also significantly reduce performance." >&2;}

Completed in 32 milliseconds