Searched refs:specifications (Results 1 – 25 of 84) sorted by relevance
1234
125 SpecificationByOffset specifications; member158 file_private_->specifications.clear(); in ClearSpecifications()319 SpecificationByOffset *specifications = in ProcessAttributeReference() local320 &file_context->file_private_->specifications; in ProcessAttributeReference()321 SpecificationByOffset::iterator spec = specifications->find(data); in ProcessAttributeReference()322 if (spec != specifications->end()) { in ProcessAttributeReference()427 cu_context_->file_context->file_private_->specifications[offset_] = spec; in ComputeQualifiedName()
21 ;Files - standard file specifications
25 ;Files - standard file specifications
2 I have commented some of the conversions specifications because there is a bug
16 // Protocol buffer specifications for task configuration.
30 8. Interface functions must not have throw() specifications.
62 specifications, because types are going to be all over the programs.
23 exception specifications on generic, templated code. But it is trivial
47 > specifications, because types are going to be all over the programs.
18 specifications and there can be no more than six of them.
8 specifications and there can be no more than six of them. Hence the command
47 … required, free sign-up) <https://www.power.org/technology-introduction/standards-specifications>`_55 * `Various IBM specifications and white papers <https://www.power.org/documentation/?document_compa…
59 The routines from the package specifications are commented.
47 **Process for tracing a test case to previous POSIX specifications not
12 specifications, but rather test that the overall behavior specified by
36 disables exception specifications on functions containing ``_LIBCPP_ASSERT``
54 argument id; format specifications are not allowed. This allows the64 "Format specifications" are used within replacement fields contained within a69 Most built-in types implement the following options for format specifications,
53 specifications and *_implementation_* cases use the maximum limit reported by
36 specifications. We wanted to capture enough data to make deterministic
124 URL specifications in 'FILE' that include user/password before the host
14 of the MPEG specifications.