Searched refs:targets (Results 1 – 20 of 20) sorted by relevance
147 self.targets.update({168 targets = {} # type: Dict[str, Callable[..., Iterable[test_case.TestCase]]] variable in TestGenerator176 test_cases = self.targets[name](*target_args)206 for name in sorted(generator.targets):212 for name in sorted(generator.targets)), end='')214 if options.targets:218 options.targets = [os.path.basename(re.sub(r'\.data\Z', r'', target))219 for target in options.targets222 options.targets = sorted(generator.targets)223 for target in options.targets:
4 This directory contains fuzz targets.5 Fuzz targets are simple codes using the library.8 These targets were meant to be used with oss-fuzz but can be used in other contexts.15 To run the fuzz targets like oss-fuzz:24 And you can run any of the fuzz targets like `fuzz_client`.26 To run the fuzz targets without oss-fuzz, you first need to install one libFuzzingEngine (libFuzzer…35 Finally, you can run the targets like `./test/fuzz/fuzz_client`.38 Corpus generation for network traffic targets41 These targets use network traffic as inputs :49 To generate corpus for these targets, you can do the following, not fully automated steps :
3 # Test the target renaming support by adding a prefix to the targets built14 # Link against all the Mbed TLS libraries. Verifies that the targets have been
37 The name of this file and the name of the targets it defines are38 conventionally related. For the purpose of this reference, targets47 This module provides the following imported targets, if found:
21 Cortex-M and RX targets.
32 # At this point, the Mbed TLS targets should have been imported, and we can now
35 # At this point, the Mbed TLS targets should have been imported, and we can now
18 # everest is not directly linked against any mbedtls targets
16 # p256m is not directly linked against any mbedtls targets
38 option(OT_FUZZ_TARGETS "enable fuzz targets" OFF)
62 * For optimizing space for embedded targets each expression/macro94 * For optimizing space for embedded targets each dependency
3 SEGGER RTT - Real Time Transfer for embedded targets
8 # that targets are built using the proper list of include directories.13 # - MBEDTLS_TARGET_PREFIX: CMake targets are designed to be alterable by calling16 # mbedtls, mbedx509, mbedcrypto and apidoc targets.362 # additional convenience targets for Unix only
87 …NU Make and a C compiler are sufficient. Some of the more advanced build targets require some Unix…107 … is a Windows shell (for instance using mingw32-make) (in that case some targets will not be avail…196 CMake projects. You can include Mbed TLS's CMake targets yourself with:201 creates the following targets:
1271 targets work when MbedTLS is built as a subdirectory. This allows the2744 * Adds fuzz targets, especially for continuous fuzzing with OSS-Fuzz.2880 previously lead to a stack overflow on constrained targets.2967 assembly for AMD64 targets creating string literals greater than those4564 * Improved Makefiles for Windows targets by fixing library targets and making
250 # files are automatically included because the library targets declare
826 targets = { variable in PSATestGenerator
4492 targets=04514 ((++targets))4522 echo "$targets targets checked"
197 implementation of ECDH and ECDSA on P-256 only, that also targets constrained
2041 - seriesid: The Series ID for which this Probe message targets at.
