Searched refs:specifications (Results 1 – 25 of 224) sorted by relevance
123456789
3 # This file contains default system-wide suppression specifications to7 # To learn about the syntax of Abigail suppression specifications,10 # If you feel like some suppression specifications should be added to20 # [2]: https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppression-specifications.24 # Below are glibc suppression specifications75 # End of glibc suppression specifications79 # Below are suppression specifications for webkitgtk98 # End of webkitgtk suppression specifications154 # krb5 default suppression specifications162 # End of krb5 suppression specifications[all …]
19 of RemoteFusedGraphExecuteInfo which contains graph specifications.24 The graph specifications(such as graph itself, input tensors and output names)27 The specifications will be passed to a dedicated registered28 remote fused graph executor. The executor will send the graph specifications
20 Scalar. The shapes and slice specifications to use when
19 Shape `[N]`. The shapes and slice specifications to use when
64 * ``--suppressions | suppr`` <*path-to-suppression-specifications-file*>67 located at *path-to-suppression-specifications-file*. Note that71 specifications are suppressed from the output of this tool.
6 This check replaces deprecated dynamic exception specifications with36 specifications.
10 …rule 1.3.5 <http://www.codingstandard.com/rule/1-3-5-do-not-use-throw-exception-specifications/>`_.
30 // required. ID to a hardware queue description in the specifications.34 // required. ID to a render stage description in the specifications.107 optional Specifications specifications = 7 [deprecated = true]; field
126 SpecificationByOffset specifications; member159 file_private_->specifications.clear(); in ClearSpecifications()349 SpecificationByOffset *specifications = in ProcessAttributeReference() local350 &file_context->file_private_->specifications; in ProcessAttributeReference()351 SpecificationByOffset::iterator spec = specifications->find(data); in ProcessAttributeReference()352 if (spec != specifications->end()) { in ProcessAttributeReference()461 cu_context_->file_context->file_private_->specifications[offset_] = spec; in ComputeQualifiedName()
1 # See https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppression-specifications
5 /* sbit table specifications */
11 - Font specifications
2 I have commented some of the conversions specifications because there is a bug
29 specifications.
23 any standards or specifications involved, please provide the relevant details.
5 specifications follow.
11 level API, they can edit a class file without knowledge of the specifications
69 …ve.org/web/20121124005736/https://www.power.org/technology-introduction/standards-specifications>`_91 * `Various IBM specifications and white papers <https://www.power.org/documentation/?document_compa…103 * `RISC-V User-Level ISA Specification <https://riscv.org/specifications/>`_
62 specifications, because types are going to be all over the programs.
30 8. Interface functions must not have throw() specifications.
18 specifications and there can be no more than six of them.
59 The routines from the package specifications are commented.
47 **Process for tracing a test case to previous POSIX specifications not