| /freebsd/lib/libc/gen/ |
| H A D | fts.3 | 33 .Nd traverse a file hierarchy
64 on a file hierarchy, which is then supplied to
71 hierarchy.
75 one of the files contained in a directory in the hierarchy.
80 It is possible to walk the hierarchy
83 or physically (visiting symbolic links), order the walk of the hierarchy or
84 prune and/or re-visit portions of the hierarchy.
90 the structure that represents the file hierarchy itself.
94 hierarchy.
98 hierarchy.
[all …]
|
| /freebsd/contrib/mtree/ |
| H A D | mtree.8 | 64 .Nd map a directory hierarchy
84 utility compares a file hierarchy against a specification,
85 creates a specification for a file hierarchy, or modifies
89 is to compare the file hierarchy rooted in the current directory
93 missing from either the file hierarchy or the specification.
124 Print a specification for the file hierarchy originating at
145 Don't complain about files that are in the file hierarchy, but not in the
176 to each other rather than to the file hierarchy.
229 Follow all symbolic links in the file hierarchy.
280 Don't follow symbolic links in the file hierarchy, instead consider
[all …]
|
| /freebsd/contrib/llvm-project/openmp/runtime/src/ |
| H A D | kmp_dispatch_hier.h | 18 // Layer type for scheduling hierarchy
29 // Convert hierarchy type (LAYER_L1, LAYER_L2, etc.) to C-style string
52 // Structure to store values parsed from OMP_SCHEDULE for scheduling hierarchy
60 // Append a level of the hierarchy
81 // Sort the hierarchy using selection sort, size will always be small
190 * attached to the kmp_hier_top_unit_t structure in the scheduling hierarchy.
196 * kmp_hier_top_unit_t hierarchy structure
438 // Information regarding a single layer within the scheduling hierarchy
460 * Structure to implement entire hierarchy
462 * The hierarchy is kept as an array of arrays to represent the different
[all …]
|
| /freebsd/tests/sys/cddl/zfs/tests/inheritance/ |
| H A D | inherit_001_pos.ksh | 162 # value at a higher level in the data hierarchy (i.e. checksum=on) then that
163 # value propogates down the hierarchy unchanged, with the source field being
167 # down the hierarchy, the value at each level is determined by a combination
168 # of the top-level value and the current level in the hierarchy.
177 # be set to we walk back up the hierarchy sampling the mountpoint property at
196 # Walk back up the hierarchy building up the
243 # up the hierarchy.
264 # dataset hierarchy
293 # hierarchy has been set up correctly as specified in the
|
| H A D | state012.cfg | 28 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
31 # hierarchy.
35 # should propogate down the entire data hierarchy. Done for completeness
|
| H A D | state014.cfg | 28 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
31 # hierarchy.
35 # should propogate down the entire data hierarchy. Done for completeness
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/inheritance/ |
| H A D | inherit_001_pos.ksh | 155 # value at a higher level in the data hierarchy (i.e. checksum=on) then that
156 # value propagates down the hierarchy unchanged, with the source field being
160 # down the hierarchy, the value at each level is determined by a combination
161 # of the top-level value and the current level in the hierarchy.
170 # be set to we walk back up the hierarchy sampling the mountpoint property at
196 # Walk back up the hierarchy building up the
243 # up the hierarchy.
267 # dataset hierarchy
322 # verify that the dataset hierarchy has been
|
| H A D | state012.cfg | 33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
36 # hierarchy.
40 # should propagate down the entire data hierarchy. Done for completeness
|
| H A D | state014.cfg | 33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
36 # hierarchy.
40 # should propagate down the entire data hierarchy. Done for completeness
|
| /freebsd/tests/ |
| H A D | README | 22 the same hierarchy as /usr/src/ wherever possible, which in turn drives
36 * The src/tests/ hierarchy (this directory) provides generic test
40 * The src/tests/ hierarchy also includes cross-functional test programs:
47 In order to keep the src/tests/ hierarchy decoupled from the actual test
|
| /freebsd/bin/pax/ |
| H A D | pax.1 | 214 When an extracted file is a directory, the entire file hierarchy
216 All extracted files are created relative to the current file hierarchy.
234 operand is also a directory, the entire file hierarchy rooted
250 hierarchy rooted at that directory will be included.
264 operands or a member of a file hierarchy rooted at one of the
304 matches a directory, the entire file hierarchy rooted at that directory will
430 member and not the file hierarchy rooted at the directory.
492 When members of type directory are matched, the file hierarchy rooted at that
661 the file in the destination hierarchy is replaced by the file in the source
662 hierarchy or by a link to the file in the source hierarchy if the file in
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zfs_receive/ |
| H A D | zfs_receive_raw_-d.ksh | 25 # zfs receive -d should create the expected encryption hierarchy.
47 log_assert "zfs receive -d should create the expected encryption hierarchy"
62 log_pass "zfs receive -d creates the expected encryption hierarchy"
|
| H A D | zfs_receive_-wR-encrypted-mix.ksh | 37 # 1. Create the dataset hierarchy
38 # 2. Snapshot the dataset hierarchy
39 # 3. Send -Rw the dataset hierarchy and receive into a top-level dataset
|
| /freebsd/bin/rm/ |
| H A D | rm.1 | 90 Attempt to remove the file hierarchy rooted in each
103 If the user does not respond affirmatively, the file hierarchy rooted in
116 When removing a hierarchy, do not cross mount points.
178 directory hierarchy:
|
| /freebsd/usr.bin/du/ |
| H A D | du.1 | 49 and for each directory in the file hierarchy rooted in each directory
51 If no file is specified, the block usage of the hierarchy rooted in
77 and gives an estimate of how much space the examined file hierarchy would
97 Display an entry for each file in a file hierarchy.
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | opt-m-include-dir.mk | 10 # To set up this scenario, the file step2.mk is created deep in a hierarchy
12 # steps up in the directory hierarchy, serving as the canary file.
42 # This is the file deep in the directory hierarchy. It sets up the
|
| /freebsd/sys/contrib/device-tree/Bindings/power/ |
| H A D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
24 match the Power Area Hierarchy in the Power Domain Specifications section of
52 This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
| H A D | renesas,sysc-rmobile.yaml | 36 This node contains a hierarchy of PM domain nodes, which should match the
37 Power Area Hierarchy in the Power Domain Specifications section of the
90 // This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
| /freebsd/contrib/llvm-project/llvm/lib/Target/SPIRV/Analysis/ |
| H A D | SPIRVConvergenceRegionAnalysis.h | 11 // hierarchy.
38 // Describes a hierarchy of convergence regions.
85 // Write to the debug output this region's hierarchy.
90 // Holds a ConvergenceRegion hierarchy.
|
| /freebsd/share/doc/psd/01.cacm/ |
| H A D | p1 | 393 important, to avoid the separation of portions of the hierarchy.
440 it is not necessary that the entire file system hierarchy
449 containing its own directory hierarchy.
458 replaces a leaf of the hierarchy tree (the ordinary file)
459 by a whole new subtree (the hierarchy stored on the
482 no link may exist between one file system hierarchy and
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/msm/ |
| H A D | qcom,idle-state.txt | 18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
20 cache hierarchy is also out of standby, and then the cpu is allowed to resume
39 system state including cache hierarchy is ready before allowing core to
|
| /freebsd/sys/contrib/device-tree/Bindings/cpu/ |
| H A D | cpu-topology.txt | 9 In a SMP system, the hierarchy of CPUs is defined through three entities that
17 The bottom hierarchy level sits at core or thread level depending on whether
21 threads existing in the system and map to the hierarchy level "thread" above.
23 in the system and map to the hierarchy level "core" above.
26 corresponding to the system hierarchy; syntactically they are defined as device
33 correspond to physical CPUs and are to be mapped to the hierarchy levels.
92 levels) since name uniqueness will be guaranteed by the device tree hierarchy.
|
| /freebsd/tools/tools/vimage/ |
| H A D | vimage.8 | 72 privileges can create and manage a hierarchy of subordinated virtual images.
112 the current one in the hierarchy.
121 current level in the vimage hierarchy.
|
| /freebsd/contrib/llvm-project/clang/lib/ExtractAPI/Serialization/ |
| H A D | SymbolGraphSerializer.cpp | 604 /// Walk the records parent information in reverse to generate a hierarchy
698 return Array(map_range(Hierarchy, [](auto Elt) { return Elt.Name; })); in serializePathComponents()
777 // If the hierarchy has at least one parent and child. in serializeAPIRecord()
778 if (Hierarchy.size() >= 2) in serializeAPIRecord()
779 serializeRelationship(MemberOf, Hierarchy.back(), in serializeAPIRecord()
780 Hierarchy[Hierarchy.size() - 2], Module); in serializeAPIRecord()
790 Hierarchy.push_back(getHierarchyReference(Record, API)); in traverseAPIRecord()
793 Hierarchy.pop_back(); in traverseAPIRecord()
977 // Short-circuit walking up the class hierarchy and handle creating typedef in walkUpFromTypedefRecord()
1093 Serializer.Hierarchy = generateHierarchyFromRecord(Record); in serializeSingleSymbolSGF()
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/Tooling/Syntax/ |
| H A D | Syntax.td | 1 //===- Syntax.td - TableGen metamodel for syntax::Node hierarchy ----------===//
40 // The NodeType that this node is derived from in the Node class hierarchy.
47 // We merely specify the inheritance hierarchy here.
|