Searched refs:asserts (Results 1 – 25 of 49) sorted by relevance
12
| /openbsd/src/gnu/usr.bin/perl/cpan/Test-Simple/t/Test2/modules/API/ |
| D | InterceptResult.t | 255 is_deeply($one->asserts, [$one->[0], $one->[3]], "Got the asserts");
262 $one->asserts(in_place => 1);
|
| /openbsd/src/gnu/usr.bin/perl/cpan/Test-Simple/lib/Test2/API/ |
| D | InterceptResult.pm | 116 sub asserts { shift->grep(has_assert => @_) } subroutine
|
| /openbsd/src/gnu/llvm/llvm/utils/release/ |
| D | test-release.sh | 146 -test-asserts | --test-asserts )
|
| /openbsd/src/sbin/isakmpd/ |
| D | policy.c | 1929 char **asserts; in policy_init() local
1975 asserts = kn_read_asserts(ptr, sz, &i); in policy_init()
1980 if (asserts == (char **)NULL) in policy_init()
1991 policy_asserts = asserts; in policy_init()
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | ReleaseProcess.rst | 70 -test-asserts \
86 * For release candidates, you need ``-test-asserts``, or it won't create a
|
| D | TestingGuide.rst | 500 ; This test will be only enabled in the build with asserts.
501 ; REQUIRES: asserts
|
| D | LibFuzzer.rst | 751 asserts/crashes on invalid inputs, in-process fuzzing is not applicable.
|
| D | CMake.rst | 709 If enabled and building a debug or asserts build the CMake build system will
|
| D | Passes.rst | 1193 #. All other things that are tested by asserts spread about the code.
|
| D | JITLink.rst | 1027 distinction between contract (which should be validated with asserts and
|
| D | GettingStarted.rst | 674 libraries unoptimized, with debugging information, and asserts enabled.
|
| D | ProgrammersManual.rst | 864 terminate the program on an error input, cantFail simply asserts that the result
1170 pass. Note that ``LLVM_DEBUG()`` macros are disabled for non-asserts builds, so they
3272 Checks and asserts that alter the LLVM C++ ABI are predicated on the
|
| D | CodingStandards.rst | 1187 In the past, asserts were used to indicate a piece of code that should not be
|
| /openbsd/src/gnu/llvm/lldb/docs/resources/ |
| D | test.rst | 284 custom asserts and checks that should be preferably used (e.g.
317 **Prefer using specific asserts over the generic assertTrue/assertFalse.**.
320 several expressive asserts such as ``self.assertIn`` that automatically
323 asserts are available. LLDB also has a few custom asserts that are tailored
|
| /openbsd/src/gnu/llvm/llvm/lib/Target/ARM/ |
| D | README-Thumb.txt | 10 to abort (failure path of asserts), EH handling code, etc.
|
| D | ARMInstrThumb.td | 303 // these will always be in pairs, and asserts if it finds otherwise. Better way?
|
| /openbsd/src/gnu/llvm/lldb/docs/testsuite/ |
| D | a-detailed-walkthrough.txt | 158 And this asserts that the file 'stdout.txt' should be present after running the
|
| /openbsd/src/gnu/llvm/clang/docs/ |
| D | ThreadSafetyAnalysis.rst | 454 These are attributes on a function or method which asserts the calling thread
|
| /openbsd/src/gnu/llvm/llvm/lib/Target/Mips/ |
| D | MipsInstrFPU.td | 784 // asserts otherwise.
|
| /openbsd/src/gnu/llvm/clang/include/clang/StaticAnalyzer/Checkers/ |
| D | Checkers.td | 364 // Uninitialized value check is a mandatory dependency. This Checker asserts
|
| /openbsd/src/gnu/usr.bin/perl/dist/Storable/ |
| D | ChangeLog | 346 - enable DEBUGME tracing and asserts with -DDEBUGGING
|
| /openbsd/src/gnu/llvm/llvm/lib/Target/AMDGPU/ |
| D | VOP3Instructions.td | 652 // FIXME: GlobalISel pattern exporter fails to export a pattern like this and asserts,
|
| /openbsd/src/gnu/llvm/llvm/ |
| D | CMakeLists.txt | 577 # This CMake flag enables a more strict mode where it asserts that the type
|
| /openbsd/src/usr.bin/awk/ |
| D | FIXES.1e | 537 removed some no-effect asserts in run.c.
|
| /openbsd/src/usr.sbin/unbound/ |
| D | configure.ac | 297 AC_ARG_ENABLE(checking, AS_HELP_STRING([--enable-checking],[Enable warnings, asserts, makefile-depe…
|
12