| /mbedtls-latest/tests/scripts/ |
| D | check_test_cases.py | 68 file_name, line_number, description): argument
121 suite_name, description = script_outputs
128 description.rstrip())
162 file_name, _line_number, description): argument
165 key = ';'.join([base_name, description.decode('utf-8')])
189 file_name, line_number, description): argument
193 if description in seen:
196 seen[description])
198 if re.search(br'[\t;]', description):
201 re.search(br'[\t;]', description).group(0).decode('ascii'))
[all …]
|
| D | depends.py | 332 description = symbol
333 if exclude and re.match(exclude, description):
339 job = Job(description, config_settings, commands)
354 description = '!' + symbol
355 if exclude and re.match(exclude, description):
359 job = Job(description, config_settings, commands)
502 description=
|
| D | list_internal_identifiers.py | 26 description=(
|
| D | run_demos.py | 54 parser = argparse.ArgumentParser(description=__doc__)
|
| D | generate_server9_bad_saltlen.py | 33 parser.description = __doc__
|
| D | psa_collect_statuses.py | 103 parser = argparse.ArgumentParser(description=globals()['__doc__'])
|
| D | test_config_script.py | 156 parser = argparse.ArgumentParser(description=__doc__,
|
| D | test_psa_constant_names.py | 162 parser = argparse.ArgumentParser(description=globals()['__doc__'])
|
| /mbedtls-latest/docs/architecture/testing/ |
| D | test-framework.md | 13 …description which succinctly describes for a human audience what the test does. The first non-comm…
17 …s must be unique within a `.data` file. If you can't think of a better description, the convention…
22 * Make the description descriptive. “foo: x=2, y=4” is more descriptive than “foo #2”. “foo: 0<x<y,…
23 * Avoid changing the description of an existing test case without a good reason. This breaks the tr…
33 …ase in `ssl-opt.sh` has a description which succinctly describes for a human audience what the tes…
35 …or [unit test descriptions](#unit-test-descriptions). In addition, the description must be written…
39 …case in `compat.sh` has a description which succinctly describes for a human audience what the tes…
59 * **Platform**: a description of the platform, e.g. `Linux-x86_64` or `Linux-x86_64-gcc7-msan`.
60 * **Configuration**: a unique description of the configuration (`mbedtls_config.h`).
62 * **Test case**: the description of the test case.
|
| /mbedtls-latest/scripts/ |
| D | generate_errors.pl | 81 my $description = (defined($before) ? $before : $after);
82 $description =~ s/^\s+//;
83 $description =~ s/\n( *\*)? */ /g;
84 $description =~ s/\.?\s+$//;
85 push @matches, [$name, $value, $description];
108 my ($error_name, $error_code, $description) = @$match;
113 $description =~ s/\\/\\\\/g;
196 "${white_space} return( \"$module_name - $description\" );\n"
|
| D | abi_check.py | 296 description = None
307 description = line.strip()
322 description=description
487 metadata.description, test_data
552 description=__doc__
|
| D | config.py | 496 parser = argparse.ArgumentParser(description="""
545 def add_adapter(name, function, description): argument
546 subparser = subparsers.add_parser(name, help=description)
|
| D | lcov.sh | 59 …genhtml --title "$title" --description-file "$COVTMP/descriptions" --keep-descriptions --legend --…
|
| D | min_requirements.py | 97 parser = argparse.ArgumentParser(description=__doc__)
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-developer-guide.md | 5 For a description of the current state of drivers Mbed TLS, see our [PSA Cryptoprocessor driver dev…
26 … linkage, and to declare these functions in a **driver description file**. The driver description …
28 …description file is JSON. The structure of this JSON file is specified in the section [“Driver des…
32 * A driver description file (in JSON format).
33 …g the types required by the driver description. The names of these header files is declared in the…
34 … for the target platform defining the functions required by the driver description. Implementation…
42 The driver description can include Mbed TLS extensions (marked by the namespace "mbedtls"). Mbed TL…
|
| D | psa-driver-integration-guide.md | 5 For a description of the current state of drivers Mbed TLS, see our [PSA Cryptoprocessor driver dev…
17 Concretely speaking, a driver consists of one or more **driver description files** in JSON format a…
23 1. Pass the driver description files through the Make variable `PSA_DRIVERS` when building the libr…
|
| D | psa-driver-wrappers-codegen-migration-guide.md | 7 For a practical guide with a description of the current state of drivers Mbed TLS, see our [PSA Cry…
24 …a2 ) to render templates based on drivers that are defined using a Driver description JSON file(s).
|
| D | psa-driver-interface.md | 8 For a practical guide, with a description of the current state of drivers Mbed TLS, see our [PSA Cr…
49 …description file**. The driver description file declares which functions the driver implements and…
51 …a driver description file is JSON. The structure of this JSON file is specified in the section [“D…
55 * A driver description file (in JSON format).
56 …g the types required by the driver description. The names of these header files are declared in th…
57 …et platform defining the entry point functions specified by the driver description. Implementation…
59 How to provide the driver description file, the C header files and the object code is implementatio…
61 ### Driver description syntax
63 The concrete syntax for a driver description file is JSON.
69 #### Driver description list
[all …]
|
| /mbedtls-latest/tests/suites/ |
| D | test_suite_asn1parse.function | 172 const char *description;
175 /* Value returned by traverse_callback if description runs out. */
177 /* Value returned by traverse_callback if description has an invalid format
187 const char *rest = state->description;
211 state->description = rest;
561 const char *description,
564 /* The description string is a comma-separated list of integers.
565 * For each element in the SEQUENCE in input, description contains
574 const char *rest = description;
619 const char *description,
[all …]
|
| /mbedtls-latest/ChangeLog.d/ |
| D | 00README.md | 39 * Change description.
40 * Another change description.
43 * Yet another change description. This is a long change description that
45 * Yet again another change description.
|
| /mbedtls-latest/library/ |
| D | oid.c | 33 #define OID_DESCRIPTOR(s, name, description) { ADD_LEN(s), name, description } argument
36 #define OID_DESCRIPTOR(s, name, description) { ADD_LEN(s) } argument
354 description)
367 description)
480 description)
|
| /mbedtls-latest/programs/test/ |
| D | udp_proxy.c | 370 const char *description; member
387 elapsed_time(), buf->description, in ctx_buffer_flush()
866 outbuf[0].description = "S <- C"; in main()
871 outbuf[1].description = "S -> C"; in main()
|
| /mbedtls-latest/docs/ |
| D | psa-driver-example-and-guide.md | 24 …for the driver dispatch layer to be auto-generated using a JSON driver description file provided b…
42 - A driver description file (in JSON format).
43 …g the types required by the driver description. The names of these header files are declared in th…
44 … for the target platform defining the functions required by the driver description. Implementation…
46 …description JSON files, see [`mbedtls_test_transparent_driver.json`](https://github.com/Mbed-TLS/m…
|
| /mbedtls-latest/doxygen/ |
| D | mbedtls.doxyfile | 36 # function, we can leave the description part of the \retval command blank.
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-crypto-implementation-structure.md | 17 …ftware cryptographic functionalities can be described by a JSON driver description file as defined…
18 * Along with JSON driver description files, the PSA driver specification defines the deliverables f…
52 …` functions are generated by the build system based on the JSON driver description files of the va…
|
