Home
last modified time | relevance | path

Searched full:requirements (Results 1 – 25 of 1088) sorted by relevance

12345678910>>...44

/freebsd/contrib/llvm-project/clang/include/clang/Tooling/Refactoring/
H A DRefactoringActionRulesInternal.h49 const std::tuple<RequirementTypes...> &Requirements, in invokeRuleAfterValidatingRequirements() argument
51 // Check if the requirements we're interested in can be evaluated. in invokeRuleAfterValidatingRequirements()
53 std::make_tuple(std::get<Is>(Requirements).evaluate(Context)...); in invokeRuleAfterValidatingRequirements()
58 // requirements from Expected<> wrappers and then run it. in invokeRuleAfterValidatingRequirements()
68 /// Scans the list of requirements in a rule and visits all the refactoring
69 /// options that are used by all the requirements.
89 const std::tuple<RequirementTypes...> &Requirements, in visitRefactoringOptions() argument
91 visitRefactoringOptionsImpl(Visitor, std::get<Is>(Requirements)...); in visitRefactoringOptions()
118 createRefactoringActionRule(const RequirementTypes &... Requirements) {
127 Rule(std::tuple<RequirementTypes...> Requirements)
[all …]
H A DRefactoringActionRules.h19 /// \c RuleType rule when all of the requirements are satisfied.
23 /// requirements that have to be satisfied by the refactoring engine before
25 /// verifies that the requirements are satisfied by evaluating them (using the
27 /// any errors. Once all requirements are satisfied, the provided refactoring
28 /// rule is constructed by passing in the values returned by the requirements'
32 /// The separation of requirements, their evaluation and the invocation of the
34 /// - Disable refactoring action rules whose requirements are not supported.
40 createRefactoringActionRule(const RequirementTypes &... Requirements);
43 /// requirements.
H A DRefactoringActionRuleRequirements.h25 /// requirements are satisfied.
35 /// constructor (provided all other requirements are satisfied).
113 /// The ownership of the option is shared among the different requirements
/freebsd/crypto/openssl/doc/designs/quic-design/
H A Dquic-requirements.md1 QUIC Requirements
4 There have been various sources of requirements for the OpenSSL QUIC
5 implementation. The following sections summarise the requirements obtained from
8 Original OMC Requirements
11 The OMC have specified an initial set of requirements for QUIC as well as other
12 requirements for the coming releases. The remainder of this section summarises
13 the OMC requirements that were originally
67 ### Non-QUIC OpenSSL Requirements argument
69 In addition to the QUIC requirements, the OMC also required that:
78 OMC Blog post requirements
[all …]
H A Ddemuxer.md7 Demuxer requirements for MVP
10 These are the requirements that were identified for MVP:
18 Optional demuxer requirements
27 Demuxer requirements for server
30 Further requirements after MVP for server support:
/freebsd/sys/contrib/edk2/Include/
H A DBase.h816 …sizeof (BOOLEAN) == 1, "sizeof (BOOLEAN) does not meet UEFI Specification Data Type requirements");
817 …T (sizeof (INT8) == 1, "sizeof (INT8) does not meet UEFI Specification Data Type requirements");
818 … (sizeof (UINT8) == 1, "sizeof (UINT8) does not meet UEFI Specification Data Type requirements");
819 … (sizeof (INT16) == 2, "sizeof (INT16) does not meet UEFI Specification Data Type requirements");
820 …(sizeof (UINT16) == 2, "sizeof (UINT16) does not meet UEFI Specification Data Type requirements");
821 … (sizeof (INT32) == 4, "sizeof (INT32) does not meet UEFI Specification Data Type requirements");
822 …(sizeof (UINT32) == 4, "sizeof (UINT32) does not meet UEFI Specification Data Type requirements");
823 … (sizeof (INT64) == 8, "sizeof (INT64) does not meet UEFI Specification Data Type requirements");
824 …(sizeof (UINT64) == 8, "sizeof (UINT64) does not meet UEFI Specification Data Type requirements");
825 … (sizeof (CHAR8) == 1, "sizeof (CHAR8) does not meet UEFI Specification Data Type requirements");
[all …]
/freebsd/contrib/arm-optimized-routines/math/
H A DREADME.contributors1 STYLE REQUIREMENTS
25 1. Math functions have quality and performance requirements.
41 - Special cases and error handling need to follow ISO C Annex F requirements,
42 POSIX requirements, IEEE 754-2008 requirements and Glibc requiremnts:
52 result should be correct (within quality requirements, which are lower for
/freebsd/contrib/llvm-project/clang/include/clang/Analysis/FlowSensitive/
H A DDataflowEnvironment.h79 /// Requirements:
101 /// Requirements:
135 /// Requirements:
174 /// Requirements:
211 /// Requirements:
233 /// Requirements:
251 /// Requirements:
265 /// Requirements:
276 /// Requirements:
289 /// Requirements:
[all …]
/freebsd/sys/dev/qlnx/qlnxe/
H A Decore_hsi_init_func.h44 * BRB RAM init requirements
56 * ETS per-TC init requirements
66 * ETS init requirements
71 struct init_ets_tc_req tc_req[NUM_OF_TCS] /* ETS initialization requirements per TC. */;
75 * NIG LB RL init requirements
95 * NIG priority to TC map init requirements
H A Decore_init_fw_funcs.h224 * Based on weight/priority requirements per-TC.
228 * @param req - the NIG ETS initialization requirements.
231 * requirements are ignored when is_lb is cleared.
241 * Based on global and per-TC rate requirements
245 * @param req - the NIG LB RLs initialization requirements.
271 * Based on weight/priority requirements per-TC.
275 * @param req - the PRS ETS initialization requirements.
287 * Based on weight/priority requirements per-TC.
291 * @param req - the BRB RAM initialization requirements.
/freebsd/contrib/llvm-project/llvm/lib/Target/SPIRV/
H A DSPIRVModuleAnalysis.h44 struct Requirements { struct
51 Requirements(bool IsSatisfiable = false, argument
57 Requirements(Capability::Capability Cap) : Requirements(true, {Cap}) {} in Requirements() argument
104 // Add the given requirements to the lists. If constraints conflict, or these
105 // requirements cannot be satisfied, then abort the compilation.
106 void addRequirements(const Requirements &Req);
110 // Check if all the requirements can be satisfied for the given subtarget, and
/freebsd/contrib/arm-optimized-routines/
H A DREADME11 contribution requirements are documented in README.contributors of
24 requirements stated in math/README.contributors,
31 meet quality requirements stated in
42 requirements stated in string/README.contributors,
/freebsd/sys/dev/ath/ath_hal/
H A Dah_regdomain.h34 * capability/requirements per regdomain.
57 * The following are flags for different requirements per reg domain.
58 * These requirements are either inhereted from the reg domain pair or
93 uint32_t flags5GHz; /* Requirements flags (AdHoc
96 uint32_t flags2GHz; /* Requirements flags (AdHoc
/freebsd/contrib/llvm-project/llvm/lib/Target/AMDGPU/
H A DSIModeRegister.cpp243 // - if this instruction's requirements are compatible with the current setting
250 // entry requirements in which case the insertion is deferred until Phase 3
262 // requirements for the block, and need to defer the first InsertionPoint to in processBlockPhase1()
265 // initial requirements. in processBlockPhase1()
298 // If we haven't already set the initial requirements for the block we in processBlockPhase1()
299 // don't need to as the requirements start from this explicit setreg. in processBlockPhase1()
306 // This instruction uses the Mode register and its requirements aren't in processBlockPhase1()
339 // If we haven't yet set the initial requirements for the block we set them in processBlockPhase1()
417 // check whether the predecessor mode meets the block's entry requirements. If
448 // instructions for intra block requirements. in runOnMachineFunction()
/freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/
H A DMachineMemOperand.h164 /// Atomic ordering requirements for this memory operation. For cmpxchg
165 /// atomic operations, atomic ordering requirements when store occurs.
167 /// For cmpxchg atomic operations, atomic ordering requirements when store
187 /// and atomic ordering requirements must also be specified. For cmpxchg
188 /// atomic operations the atomic ordering requirements when store does not
275 /// Return the atomic ordering requirements for this memory operation. For
276 /// cmpxchg atomic operations, return the atomic ordering requirements when
282 /// For cmpxchg atomic operations, return the atomic ordering requirements
/freebsd/contrib/llvm-project/libcxx/include/__algorithm/
H A Duniform_random_bit_generator_adaptor.h29 // Classic algorithms require the given generator to meet the uniform random bit generator requirements; these
30 // requirements include satisfying `std::uniform_random_bit_generator` and add a requirement for the generator to
33 // To be able to reuse classic implementations, make the given generator meet the classic requirements by wrapping
/freebsd/contrib/libcbor/
H A D.gitignore11 # No top-level requirements, see doc/source
12 requirements.txt
/freebsd/share/man/man7/
H A Dsdoc.748 describing what security requirements can be broken
64 those general security requirements that can be violated
66 There are four classes of security requirements:
190 Let your list of potentially-violated security requirements
/freebsd/contrib/llvm-project/clang/lib/Basic/
H A DModule.cpp142 for (unsigned I = 0, N = Current->Requirements.size(); I != N; ++I) { in isUnimportable()
143 if (hasFeature(Current->Requirements[I].FeatureName, LangOpts, Target) != in isUnimportable()
144 Current->Requirements[I].RequiredState) { in isUnimportable()
145 Req = Current->Requirements[I]; in isUnimportable()
322 Requirements.push_back(Requirement{std::string(Feature), RequiredState}); in addRequirement()
501 if (!Requirements.empty()) { in print()
504 for (unsigned I = 0, N = Requirements.size(); I != N; ++I) { in print()
507 if (!Requirements[I].RequiredState) in print()
509 OS << Requirements[I].FeatureName; in print()
/freebsd/contrib/llvm-project/lld/docs/
H A Derror_handling_script.rst7 when certain errors are encountered. This document specifies the requirements of
10 Generic Requirements
/freebsd/sys/contrib/device-tree/Bindings/iio/adc/
H A Dvf610-adc.txt16 requirements. Three values are required, depending on conversion mode:
23 operating requirements. A safe default across a wide range of R_as and
/freebsd/sys/contrib/device-tree/Bindings/display/panel/
H A Dolimex,lcd-olinuxino.yaml21 - AT24C16C EEPROM holding panel identification and timing requirements
27 device information (id, serial, etc.) and timing requirements.
/freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/Vectorize/
H A DLoopVectorizationLegality.h201 /// This holds vectorization requirements that must be verified late in
202 /// the process. The requirements are set by legalize and costmodel. Once
204 /// requirements can be verified by looking for metadata or compiler options.
208 /// Late evaluation of these requirements allows helpful diagnostics to be
249 ORE(ORE), Requirements(R), Hints(H), DB(DB), AC(AC), BFI(BFI), in LoopVectorizationLegality()
526 /// Vectorization requirements that will go through late-evaluation.
527 LoopVectorizationRequirements *Requirements; variable
/freebsd/sys/contrib/device-tree/Bindings/firmware/
H A Dqcom,scm.txt46 clock and "bus" for the bus clock per the requirements of the compatible.
49 - interconnects: Specifies the bandwidth requirements of the SCM interface (optional)
/freebsd/share/man/man4/
H A Dfdtbus.471 Core Requirements and Practices
74 Power.org Standard for Embedded Power Architecture Platform Requirements

12345678910>>...44